[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type.
** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Won't Fix ** Changed in: linux-kvm (Ubuntu Cosmic) Status: New => Won't Fix ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Focal) Status: New => Confirmed ** Summary changed: - fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type. + fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type. (config not enabled) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812622 Title: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type. (config not enabled) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Won't Fix Status in linux-kvm source package in Cosmic: Won't Fix Status in linux source package in Eoan: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Status in linux source package in Focal: New Status in linux-aws source package in Focal: New Status in linux-kvm source package in Focal: Confirmed Bug description: These tests: * fib_tests.sh * fib-onlink-tests.sh * fib_rule_tests.sh All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not supported: selftests: net: fib_tests.sh Single path route test RTNETLINK answers: Operation not supported not ok 1..11 selftests: net: fib_tests.sh [FAIL] selftests: net: fib-onlink-tests.sh Configuring interfaces RTNETLINK answers: Operation not supported not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL] selftests: net: fib_rule_tests.sh RTNETLINK answers: Operation not supported not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL] (works on generic Cosmic kernel) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6 ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17 Uname: Linux 4.18.0-1006-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Mon Jan 21 08:00:22 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+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 1938976] Re: linux-gke: Do not build/ship aufs.ko
** Changed in: linux-gke-5.4 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/1938976 Title: linux-gke: Do not build/ship aufs.ko Status in linux-gke package in Ubuntu: In Progress Status in linux-gke-5.4 package in Ubuntu: Invalid Status in linux-gke-5.4 source package in Bionic: Fix Released Status in linux-gke source package in Focal: Fix Released Bug description: See https://partnerissuetracker.corp.google.com/issues/194431474 for more information [Impact] aufs.ko to be removed [Fix] Set CONFIG_AUFS_FS to N. [Test] Confirm that aufs.ko no longer being built. [Regression Potential] No expected regression (aufs functionality will be disabled) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/1938976/+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 1929889] Re: [TGL][ADL] Enable CET(Control-flow Enforcement Technology)
@Dimitri Intel has done a few experiments to enable CET on Ubuntu 20.04. Here are some details: As my experiment in ubuntu 20.04, the glibc should be update into 2.34. And busybox should be build on glibc 2.34 (to create initramfs during install kernel). Then ubuntu 20.04 can start, and cet enabled. Diff glibc 2.31 and glib 2.34 listed as below(20.04 basic glibc is 2.31, 21.04 is 2.34) ea26ff0322 x86: Copy IBT and SHSTK usable only if CET is enabled 04dff6fc0d x86: Properly set usable CET feature bits [BZ #26625] 2ef23b5205 x86: Set header.feature_1 in TCB for always-on CET [BZ #27177] c02695d776 x86/CET: Update vfork to prevent child return 9e38f455a6 x86: Add --enable-cet=permissive 674ea88294 x86: Move CET control to _dl_x86_feature_control [BZ #25887] 1fabdb9908 x86: Remove ARCH_CET_LEGACY_BITMAP [BZ #25397] 5d844e1b72 i386: Enable CET support in ucontext functions 0455f251f4 i386: Use ENTRY/END in assembly codes 825b58f3fb i386-mcount.S: Add _CET_ENDBR to _mcount and __fentry__ 4031d7484a i386/sub_n.S: Add a missing _CET_ENDBR to indirect jump target 15eab1e3e8 i386: Don't unnecessarily save and restore EAX, ECX and EDX [BZ# 25262] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929889 Title: [TGL][ADL] Enable CET(Control-flow Enforcement Technology) Status in intel: New Status in intel lookout-canyon series: New Status in linux-intel package in Ubuntu: Triaged Status in linux-intel source package in Focal: New Bug description: Description Enable Tiger Lake ROP CET(Control-flow Enforcement Technology) An upcoming Intel® processor family feature that counters return/jump-oriented programming (ROP) attacks Hardware: Tiger Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929889/+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 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
fixed in 1.2.5.1-2 which is in impish and up ** Changed in: alsa-topology-conf (Ubuntu Impish) Status: New => Fix Released ** Changed in: alsa-topology-conf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-topology-conf in Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in alsa-topology-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in alsa-topology-conf source package in Focal: New Status in alsa-ucm-conf source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in alsa-topology-conf source package in Hirsute: New Status in alsa-ucm-conf source package in Hirsute: Won't Fix Status in linux source package in Hirsute: Fix Released Status in alsa-topology-conf source package in Impish: Fix Released Status in alsa-ucm-conf source package in Impish: Won't Fix Status in linux source package in Impish: Fix Released Bug description: [SRU Justification] [Impact] Skylake, Kabylake, Kabylake-refresh, Amberlake and some other platforms where audio is of SPT (PCH) type, HDA (with DSP capabilities) plus DMIC configuration is supported on these with skylake driver since kernel 5.8. However, no sound card can be detected w/o the topology binary file in /lib/firmware and corresponding ucm file. [Fix] The kernel config CONFIG_SND_SOC_INTEL_SKYLAKE_HDAUDIO_CODEC needa to be enabled for the snd_soc_skl driver to support HDA+DMIC configuration. And the topology binary file and UCM files need to be located in the correct path based on Intel's suggestion. https://gist.github.com/crojewsk/4e6382bfb0dbfaaf60513174211f29cb. [Test] On the Skylake/Kabylake platforms with either the PCI device 8086:9d70 and 8086:9d71, boot up the machine and check the existence of the sound card by either 'aplay -l' or 'pactl list' command. [Where problems could occur] Should be low risk, it only affects limited Intel Platforms with particular PCI device IDs + HDA plus DMIC configuration. == Original Bug Description == Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11
[Kernel-packages] [Bug 1951917] [NEW] battery drain even after poweroff
Public bug reported: Battery drain even after poweroff. Incorrect battery charge reading. Please fix this bug as quickly as possible. It's very annoying. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-40-generic 5.11.0-40.44~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 23 11:44:08 2021 InstallationDate: Installed on 2020-09-21 (428 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1951917 Title: battery drain even after poweroff Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Battery drain even after poweroff. Incorrect battery charge reading. Please fix this bug as quickly as possible. It's very annoying. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-40-generic 5.11.0-40.44~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 23 11:44:08 2021 InstallationDate: Installed on 2020-09-21 (428 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1951917/+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 1938998] 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/1938998 Title: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+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 1938998] Re: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly
Is this bug still happening? If so then with what package versions? ** Tags added: focal ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1938998 Title: [vmwgfx] Update to mesa and xorg-server causes Cinnamon desktop to not render properly Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: On a VMWare Workstation VM running Linux Mint 20.1 (64-bit) with Cinnamon 4.8.6 or Linux Mint 20.2 (64-bit) with Cinnamon 5.0.5, upgrading to a specific mesa and xorg-server version, followed by a system restart, led to the Cinnamon desktop not rendering correctly, such that the desktop was unusable. The rendering problem is that icons and menus are displayed as grey rectangles and it's not possible to see what they are. I believe the problem is in one of these packages: * mesa 21.0.3-0ubuntu0.2-20.04.1 * xorg-server 2:1.20.11-1ubuntu1-20.04.2 Restoring the system from backup, and then upgrading but omitting the above two updates and restarting, the system behaves as expected. It's not immediately clear which of these packages is causing the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vinay 1218 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-01-30 (187 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: lono wireless extensions. ens33 no wireless extensions. tailscale0 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/7p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=681c361f-49a2-4943-94c0-abb7554046f8 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 RelatedPackageVersions: linux-restricted-modules-5.4.0-80-generic N/A linux-backports-modules-5.4.0-80-generic N/A linux-firmware1.187.15 RfKill: Tags: ulyssa Uname: Linux 5.4.0-80-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2014 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938998/+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 1951134] Re: hirsute:linux-aws ubuntu_ltp Failed test cases : fs_fill
*** This bug is a duplicate of bug 1878877 *** https://bugs.launchpad.net/bugs/1878877 It's failing with ENOSPC on btrfs: fs_fill.c:55: TBROK: unlink(mntpoint/thread5/file0) failed: ENOSPC (28) fs_fill.c:55: TBROK: unlink(mntpoint/thread6/file0) failed: ENOSPC (28) Test log: tst_test.c:932: TINFO: Formatting /dev/loop5 with btrfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s fs_fill.c:103: TINFO: Running 10 writer threads tst_fill_fs.c:59: TINFO: write(): ENOSPC (28) tst_fill_fs.c:59: TINFO: write(): ENOSPC (28) tst_fill_fs.c:59: TINFO: write(): ENOSPC (28) tst_fill_fs.c:59: TINFO: write(): ENOSPC (28) fs_fill.c:53: TINFO: Unlinking mntpoint/thread3/file0 fs_fill.c:53: TINFO: Unlinking mntpoint/thread8/file0 tst_fill_fs.c:59: TINFO: write(): ENOSPC (28) fs_fill.c:53: TINFO: Unlinking mntpoint/thread5/file0 fs_fill.c:53: TINFO: Unlinking mntpoint/thread6/file0 tst_fill_fs.c:59: TINFO: write(): ENOSPC (28) tst_fill_fs.c:59: TINFO: write(): ENOSPC (28) tst_fill_fs.c:59: TINFO: write(): ENOSPC (28) fs_fill.c:53: TINFO: Unlinking mntpoint/thread2/file0 fs_fill.c:55: TBROK: unlink(mntpoint/thread5/file0) failed: ENOSPC (28) fs_fill.c:55: TBROK: unlink(mntpoint/thread6/file0) failed: ENOSPC (28) fs_fill.c:53: TINFO: Unlinking mntpoint/thread1/file0 fs_fill.c:53: TINFO: Unlinking mntpoint/thread10/file0 fs_fill.c:53: TINFO: Unlinking mntpoint/thread9/file0 ** This bug has been marked a duplicate of bug 1878877 fs_fill in fs from ubuntu_ltp failed with ENOSPC when testing btrfs on B-5.3 ARM64 / P9, B-5.4, H-5.11 aws -- 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/1951134 Title: hirsute:linux-aws ubuntu_ltp Failed test cases : fs_fill Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Bug description: INFO | Failed test cases : fs_fill To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951134/+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 1949353] Re: [SRU] Revert 'e1000e: add handshake with the Intel CSME to support S0ix'
*** This bug is a duplicate of bug 1951861 ***
https://bugs.launchpad.net/bugs/1951861
https://lists.ubuntu.com/archives/kernel-team/2021-November/125883.html
BugLink: https://bugs.launchpad.net/bugs/1951861
[Impact]
e1000e devices stop working after s2idle resume.
[Fix]
Revert the offending patch series, which is to bring some minor power
saving.
[Test]
Vendor did extensive tests and didn't find any regression, and the power
consumption remains the same.
[Where problems could occur]
Maybe on some system the series can save some energy, so reverting will
cause some power consumption increase.
Kai-Heng Feng (3):
Revert "e1000e: Additional PHY power saving in S0ix"
Revert "e1000e: Add polling mechanism to indicate CSME DPG exit"
Revert "e1000e: Add handshake with the CSME to support S0ix"
drivers/net/ethernet/intel/e1000e/ich8lan.h | 3 -
drivers/net/ethernet/intel/e1000e/netdev.c | 358 +---
drivers/net/ethernet/intel/e1000e/regs.h| 1 -
3 files changed, 154 insertions(+), 208 deletions(-)
** This bug has been marked a duplicate of bug 1951861
Fix non-working e1000e device after resume
--
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/1949353
Title:
[SRU] Revert 'e1000e: add handshake with the Intel CSME to support
S0ix'
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
Incomplete
Bug description:
[SRU Justification]
https://patchwork.ozlabs.org/project/ubuntu-kernel/list/?series=258514
From the 5.13.0-1012-oem kernel we found NO Ethernet connecting after resume
from suspend, on 5.13.0-1010-oem we don't met this issue, so this is a
regression on I219 in lots of platforms.
And this blocked our OEM projects, could we revert the patches in short term?
When the firmware or the related patches are ready, we merge it again.
Oct 25 22:45:44 p15s-ThinkPad-P15s-Gen-2i kernel: e1000e :00:1f.6
enp0s31f6: Detected Hardware Unit Hang:
TDH <3>
TDT <7>
next_to_use <7>
next_to_clean <3>
buffer_info[next_to_clean]:
time_stamp
next_to_watch <3>
jiffies
next_to_watch.status <0>
MAC Status <40080283>
PHY Status <796d>
PHY 1000BASE-T Status <3800>
PHY Extended Status <3000>
PCI Status <10>
[Impact]
These doesn't improve power consumption on some e1000e platforms.
[Fix]
I tried to revert these 3 patches on 5.13.0-1019.23, it works fine.
commit f65d71bdcb52e8d82dd0a3e71ae4359c0972fe3b
Author: Sasha Neftin
Date: Wed Aug 18 15:10:49 2021 +0800
e1000e: Additional PHY power saving in S0ix
BugLink: https://bugs.launchpad.net/bugs/1937252
After transferring the MAC-PHY interface to the SMBus set the PHY
to S0ix low power idle mode
commit c97933898708a37678ba1fc6f1f5704fbe92774c
Author: Sasha Neftin
Date: Wed Aug 18 15:10:48 2021 +0800
e1000e: Add polling mechanism to indicate CSME DPG exit
BugLink: https://bugs.launchpad.net/bugs/1937252
Per guidance from the CSME architecture team, it may take
up to 1 second for unconfiguring dynamic power gating mode.
Practically it can take more time. Wait up to 2.5 seconds to indicate
dynamic power gating exit from the S0ix configuration. Detect
scenarios that take more than 1 second but less than 2.5 seconds
will emit warning message.
commit 66069cb4ebaf0eccfdec934ebfd92d3fdb136adc
Author: Sasha Neftin
Date: Wed Aug 18 15:10:47 2021 +0800
e1000e: Add handshake with the CSME to support S0ix
BugLink: https://bugs.launchpad.net/bugs/1937252
On the corporate system, the driver will ask from the CSME
(manageability engine) to perform device settings are required
to allow S0ix residency.
This patch provides initial support.
[Test Case]
Do suspend and resume 10 times, it works fine.
for i in {1..10}; do
echo $i
rtcwake -m no -s 20 && echo mem > /sys/power/state
if dmesg | grep -q "Detected Hardware Unit Hang"; then
exit
fi
sleep 15
done
[Where problems could occur]
00:1f.6 Ethernet
[Kernel-packages] [Bug 1951861] Re: Fix non-working e1000e device after resume
** Tags added: originate-from-1948738 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951861 Title: Fix non-working e1000e device after resume Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e devices stop working after s2idle resume. [Fix] Revert the offending patch series, which is to bring some minor power saving. [Test] Vendor did extensive tests and didn't find any regression, and the power consumption remains the same. [Where problems could occur] Maybe on some system the series can save some energy, so reverting will cause some power consumption increase. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944667] Re: High CPU usage in Xorg with NVIDIA reverse prime external monitor
[Expired for xserver-xorg-video-amdgpu (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1944667 Title: High CPU usage in Xorg with NVIDIA reverse prime external monitor Status in nvidia-graphics-drivers-470 package in Ubuntu: Expired Status in xserver-xorg-video-amdgpu package in Ubuntu: Expired Bug description: With my Legion Slim 7 in hybrid graphics mode (using amdgpu to drive the laptop display) and an external monitor connected via the nvidia card on a USB-C/HDMI connection, Xorg consistently uses around 40% CPU even with no apps running. If I put the laptop in discrete graphics mode so the nvidia card drives both the laptop display and the external monitor Xorg uses close to 0% CPU, which is what I would expect it to be in hybrid mode. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-core 2:1.20.13-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Thu Sep 23 11:48:15 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.13.0-16-generic, x86_64: installed nvidia, 470.63.01, 5.14.5-051405-generic, x86_64: installed nvidia, 470.63.01, 5.15.0-051500rc2-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q] [17aa:3801] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:380c] InstallationDate: Installed on 2021-09-15 (8 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 82K8 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet splash amdgpu.backlight=0 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: HACN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 15ACH6 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6: dmi.product.family: Legion S7 15ACH6 dmi.product.name: 82K8 dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6 dmi.product.version: Legion S7 15ACH6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1944667/+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 1944667] Re: High CPU usage in Xorg with NVIDIA reverse prime external monitor
[Expired for nvidia-graphics-drivers-470 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1944667 Title: High CPU usage in Xorg with NVIDIA reverse prime external monitor Status in nvidia-graphics-drivers-470 package in Ubuntu: Expired Status in xserver-xorg-video-amdgpu package in Ubuntu: Expired Bug description: With my Legion Slim 7 in hybrid graphics mode (using amdgpu to drive the laptop display) and an external monitor connected via the nvidia card on a USB-C/HDMI connection, Xorg consistently uses around 40% CPU even with no apps running. If I put the laptop in discrete graphics mode so the nvidia card drives both the laptop display and the external monitor Xorg uses close to 0% CPU, which is what I would expect it to be in hybrid mode. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xserver-xorg-core 2:1.20.13-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-5ubuntu1) ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Thu Sep 23 11:48:15 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.13.0-16-generic, x86_64: installed nvidia, 470.63.01, 5.14.5-051405-generic, x86_64: installed nvidia, 470.63.01, 5.15.0-051500rc2-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2560] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA106M [GeForce RTX 3060 Mobile / Max-Q] [17aa:3801] Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Lenovo Cezanne [17aa:380c] InstallationDate: Installed on 2021-09-15 (8 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 82K8 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.13.0-16-generic root=UUID=99f436de-d37c-4b3e-adb2-612443efc197 ro rootflags=subvol=@ quiet splash amdgpu.backlight=0 vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2021 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: HACN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion S7 15ACH6 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrHACN27WW:bd08/02/2021:br1.27:efr1.27:svnLENOVO:pn82K8:pvrLegionS715ACH6:skuLENOVO_MT_82K8_BU_idea_FM_LegionS715ACH6:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLegionS715ACH6: dmi.product.family: Legion S7 15ACH6 dmi.product.name: 82K8 dmi.product.sku: LENOVO_MT_82K8_BU_idea_FM_Legion S7 15ACH6 dmi.product.version: Legion S7 15ACH6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1944667/+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 1950720] Re: GSYNC bug regression in 495.44 Ubuntu 21.10
** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1950720 Title: GSYNC bug regression in 495.44 Ubuntu 21.10 Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-495 package in Ubuntu: New Bug description: Similar to bug https://launchpad.net/bugs/1950665, the GSYNC regression bug has returned in 495.44 on Ubuntu 21.10. I have tried the standard kernel and 5.14.1 and 5.14.17, but they are all experiencing the same bug again. Hardware is: - NVIDIA GeForce RTX 2080 Super - Dell 27" S2721DGF G-Sync Compatible monitor - High quality DisplayPort cable (This was replaced previously under suspicion) This issue happens at all refresh rates: 60 Hz, 120 Hz, 144 Hz and 165 Hz. Prior to upgrading to Ubuntu 21.10, I had upgraded to 495.44 on Ubuntu 21.04 and kernel 5.14.1, and this problem was not present. I then upgraded to Ubuntu 21.10, and the problem didn't seem to be present, but as of today I've noticed again. I'm not sure what the cause is, but I have tried full driver purges, returned to 470.82, went back to the standard kernel for 21.10 (5.13.0-21-generic), 5.14.1 and 5.14.17, and the problem continues to occur when any GPU accelerated application starts, in some cases when switching between applications (i.e. alt tabbing out of a game). A second or so of no signal occurs as it re-syncs. I am unsure if X11 has been updated in this time, I know there was work happening on GBM support, wondering if X11 has switched to using this instead of the EGL Streams direct approach that was used previously. Either-way, I'm still running X11 in all of these tests. Let me know if there are any tests you'd like me to try. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1950720/+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 1945367] Re: [nvidia] Graphics freeze
** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945367 Title: [nvidia] Graphics freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Bug description: i open a second bug report because i have already freeze problem after the installation of nvidia drivers and reboot. Freeze become generally when i am using firefox and visioning a video with youtube. I specify that since the last bug report, i re install ubuntu with official .iso without other package non official. To create the report, i have to connect to the PC from another one with ssh. When i use ubuntu-bug, it is not possible to join nvidia-bug-report because the application dont give me the hand to finish the report. When i try to execute nvidia-bug-report, i have the same thing. To use the PC, i have to use nouveau drivers and intel Xe GPU with poor performances ... Thanks for help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Tue Sep 28 21:13:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2090] NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2090] InstallationDate: Installed on 2021-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Intel(R) Client Systems NUC11PHi7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=24658b6f-3e37-4376-bc2e-2207e961c9c8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: PHTGL579.0063.2021.0707.1057 dmi.board.name: NUC11PHBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M26151-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 12.19 dmi.modalias: dmi:bvnIntelCorp.:bvrPHTGL579.0063.2021.0707.1057:bd07/07/2021:br5.19:efr12.19:svnIntel(R)ClientSystems:pnNUC11PHi7:pvrM26149-403:skuSWNUC11PHKi7C00:rvnIntelCorporation:rnNUC11PHBi7:rvrM26151-402:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: PH dmi.product.name: NUC11PHi7 dmi.product.sku: SWNUC11PHKi7C00 dmi.product.version: M26149-403 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1945367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1951883] [NEW] Focal update: v5.4.157 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.157 upstream stable release from git://git.kernel.org/ ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned ARM: 9134/1: remove duplicate memcpy() definition ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype ARM: 9141/1: only warn about XIP address when not compile testing ipv6: use siphash in rt6_exception_hash() ipv4: use siphash instead of Jenkins in fnhe_hashfun() usbnet: sanity check for maxpacket usbnet: fix error return code in usbnet_probe() Revert "pinctrl: bcm: ns: support updated DT binding as syscon subnode" ata: sata_mv: Fix the error handling of mv_chip_id() nfc: port100: fix using -ERRNO as command type mask net/tls: Fix flipped sign in tls_err_abort() calls mmc: vub300: fix control-message timeouts mmc: cqhci: clear HALT state after CQE enable mmc: dw_mmc: exynos: fix the finding clock sample value mmc: sdhci: Map more voltage level to SDHCI_POWER_330 mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit cfg80211: scan: fix RCU in cfg80211_add_nontrans_list() net: lan78xx: fix division by zero in send path tcp_bpf: Fix one concurrency problem in the tcp_bpf_send_verdict function IB/qib: Protect from buffer overflow in struct qib_user_sdma_pkt fields IB/hfi1: Fix abba locking issue with sc_disable() nvmet-tcp: fix data digest pointer calculation nvme-tcp: fix data digest pointer calculation RDMA/mlx5: Set user priority for DCT arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node regmap: Fix possible double-free in regcache_rbtree_exit() net: batman-adv: fix error handling net: Prevent infinite while loop in skb_tx_hash() RDMA/sa_query: Use strscpy_pad instead of memcpy to copy a string nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST net: ethernet: microchip: lan743x: Fix driver crash when lan743x_pm_resume fails net: ethernet: microchip: lan743x: Fix dma allocation failure by using dma_set_mask_and_coherent net: nxp: lpc_eth.c: avoid hang when bringing interface down net/tls: Fix flipped sign in async_wait.err assignment phy: phy_ethtool_ksettings_get: Lock the phy for consistency phy: phy_start_aneg: Add an unlocked version sctp: use init_tag from inithdr for ABORT chunk sctp: fix the processing for INIT_ACK chunk sctp: fix the processing for COOKIE_ECHO chunk sctp: add vtag check in sctp_sf_violation sctp: add vtag check in sctp_sf_do_8_5_1_E_sa sctp: add vtag check in sctp_sf_ootb net: use netif_is_bridge_port() to check for IFF_BRIDGE_PORT cfg80211: correct bridge/4addr mode check KVM: s390: clear kicked_mask before sleeping again KVM: s390: preserve deliverable_mask in __airqs_kick_single_vcpu perf script: Check session->header.env.arch before using it Linux 5.4.157 UBUNTU: upstream stable to v5.4.157 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.157 upstream stable release + from
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
@arighi that would be great. when you ping them you should mention that the release notes need to have a "Known issue" added at the very least. cheers. -- 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/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Status in linux source package in Jammy: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1949721] Re: [HUAWAI MateBook 14 2021] Sound not working
This is also affecting me. Has anyone located a workaround? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1949721 Title: [HUAWAI MateBook 14 2021] Sound not working Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 and the sound is not working on the fresh install. The microphone either. I have 5 computers with same hardware. Same problem everywhere. I guess there is a missing driver. Here is lspci output: 00:00.0 Host bridge: Intel Corporation Device 9a14 (rev 01) 00:02.0 VGA compatible controller: Intel Corporation Device 9a49 (rev 01) 00:04.0 Signal processing controller: Intel Corporation Device 9a03 (rev 01) 00:14.0 USB controller: Intel Corporation Device a0ed (rev 20) 00:14.2 RAM memory: Intel Corporation Device a0ef (rev 20) 00:14.3 Network controller: Intel Corporation Device a0f0 (rev 20) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a0e8 (rev 20) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a0e9 (rev 20) 00:15.2 Serial bus controller [0c80]: Intel Corporation Device a0ea (rev 20) 00:16.0 Communication controller: Intel Corporation Device a0e0 (rev 20) 00:1d.0 PCI bridge: Intel Corporation Device a0b0 (rev 20) 00:1f.0 ISA bridge: Intel Corporation Device a082 (rev 20) 00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) 00:1f.4 SMBus: Intel Corporation Device a0a3 (rev 20) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Device a0a4 (rev 20) 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd Device a809 Here is lspci -v output about audio: 00:1f.3 Multimedia audio controller: Intel Corporation Device a0c8 (rev 20) Subsystem: QUANTA Computer Inc Device 1307 Flags: bus master, fast devsel, latency 32, IRQ 147 Memory at 600112 (64-bit, non-prefetchable) [size=16K] Memory at 600100 (64-bit, non-prefetchable) [size=1M] Capabilities: Kernel driver in use: sof-audio-pci Kernel modules: snd_hda_intel, snd_sof_pci The pa-info output is in attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1949721/+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 1951880] [NEW] Impish update: upstream stable patchset 2021-11-22
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-22 Ported from the following upstream stable releases: v5.10.74, v5.14.13 v5.10.75, v5.14.14 v5.10.76, v5.14.15 from git://git.kernel.org/ ext4: check and update i_disksize properly ext4: correct the error path of ext4_write_inline_data_end() ASoC: Intel: sof_sdw: tag SoundWire BEs as non-atomic HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS netfilter: ip6_tables: zero-initialize fragment offset HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs ASoC: SOF: loader: release_firmware() on load failure to avoid batching netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic netfilter: nf_nat_masquerade: defer conntrack walk to work queue mac80211: Drop frames from invalid MAC address in ad-hoc mode m68k: Handle arrivals of multiple signals correctly hwmon: (ltc2947) Properly handle errors when looking for the external clock net: prevent user from passing illegal stab size mac80211: check return value of rhashtable_init vboxfs: fix broken legacy mount signature checking net: sun: SUNVNET_COMMON should depend on INET drm/amdgpu: fix gart.bo pin_count leak scsi: ses: Fix unsigned comparison with less than zero scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported" perf/core: fix userpage->time_enabled of inactive events sched: Always inline is_percpu_thread() hwmon: (pmbus/ibm-cffps) max_power_out swap changes ALSA: usb-audio: Unify mixer resume and reset_resume procedure KVM: arm64: nvhe: Fix missing FORCE for hyp-reloc.S build rule pinctrl: qcom: sc7280: Add PM suspend callbacks net: bgmac-platform: handle mac-address deferral scsi: qla2xxx: Fix excessive messages during device logout io_uring: kill fasync UBUNTU: upstream stable to v5.10.74, v5.14.13 ALSA: usb-audio: Add quirk for VF0770 ALSA: pcm: Workaround for a wrong offset in SYNC_PTR compat ioctl ALSA: seq: Fix a potential UAF by wrong private_free call order ALSA: hda/realtek: Enable 4-speaker output for Dell Precision 5560 laptop ALSA: hda - Enable headphone mic on Dell Latitude laptops with ALC3254 ALSA: hda/realtek: Complete partial device name to avoid ambiguity ALSA: hda/realtek: Add quirk for Clevo X170KM-G ALSA: hda/realtek - ALC236 headset MIC recording issue ALSA: hda/realtek: Add quirk for TongFang PHxTxX1 ALSA: hda/realtek: Fix the mic type detection issue for ASUS G551JW nds32/ftrace: Fix Error: invalid operands (*UND* and *UND* sections) for `^' s390: fix strrchr() implementation clk: socfpga: agilex: fix duplicate s2f_user0_clk csky: don't let sigreturn play with priveleged bits of status register csky: Fixup regs.sr broken in ptrace arm64/hugetlb: fix CMA gigantic page order for non-4K PAGE_SIZE drm/msm: Avoid potential overflow in timeout_to_jiffies() btrfs: unlock newly allocated extent buffer after error btrfs: deal with errors when replaying dir entry during log replay btrfs: deal with errors when adding inode reference during log replay btrfs: check for error when looking up inode during dir entry replay btrfs: update refs for any root except tree log roots btrfs: fix abort logic in btrfs_replace_file_extents x86/resctrl: Free the ctrlval arrays when domain_setup_mon_state() fails mei: me: add Ice Lake-N device id. USB: xhci: dbc: fix tty registration race xhci: guard accesses to ep_state in xhci_endpoint_reset() xhci: Fix command ring pointer corruption while aborting a command xhci: Enable trust tx length quirk for Fresco FL11 USB controller cb710: avoid NULL pointer subtraction efi/cper: use stack buffer for error record decoding efi: Change down_interruptible() in virt_efi_reset_system() to down_trylock() usb: musb: dsps: Fix the probe error path Input: xpad - add support for another USB ID of Nacon GC-100 USB: serial: qcserial: add EM9191 QDL support USB: serial: option: add Quectel EC200S-CN module support USB: serial: option: add Telit LE910Cx composition 0x1204 USB: serial: option: add prod. id for Quectel EG91 misc: fastrpc: Add missing lock before accessing find_vma() virtio: write back F_VERSION_1 before validate EDAC/armada-xp: Fix output of uncorrectable error counter nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells x86/Kconfig: Do not enable AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT automatically powerpc/xive: Discard disabled interrupts in get_irqchip_state() iio: adc: aspeed: set driver data when adc probe. drivers: bus: simple-pm-bus: Add support
[Kernel-packages] [Bug 1950339] Re: Screen stays black after going idle or waking up from suspend on AMD laptop
Problem persists with linux-image-generic-hwe-20.04-edge 5.13.0.22.22~20.04.9 from focal-proposed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1950339 Title: Screen stays black after going idle or waking up from suspend on AMD laptop Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Upon upgrading to the latest HWE edge kernel (from 5.11 to 5.13) on 20.04, I found that my screen won't work if my laptop goes idle (screen off) or wakes up from suspend. Reverting to 5.11 resolves this for me. This seems to be a common issue across many distributions and appears to have been fixed in 5.14. I'm using a ThinkPad P14s AMD Gen 1 with Ryzen 7 4750u (integrated graphics). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-21-generic 5.13.0-21.21~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-21.21~20.04.1-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Nov 9 10:46:08 2021 InstallationDate: Installed on 2021-07-08 (123 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1950339/+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 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
** Tags added: aws azures sru-20211108 -- 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/1949532 Title: ubuntu_ltp_controllers tests failing on Impish Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Almost half of the ubuntu_ltp_controllers tests are failing due to the general pattern 'cgroup_name already mounted or mount point busy' causing the tests to fail. e.g. mount: /dev/cgroup: ltp_cgroup already mounted or mount point busy. cgroup_fj_function2_memory 1 TBROK: mount -t cgroup -o memory ltp_cgroup /dev/cgroup failed From investigation it seems there could be an issue with the transition to cgroup-v2. There have been rumors on the ltp mailing list that one of these days the tests could break due to the transition. Switching to cgroup-v2, likely due to a systemd update, could cause these tests to break due to different mount and cgroup hierarchy semantics. I could only reproduce a subset of the new failures we are seeing, but after setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, a lot of the failures I could produce went away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+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 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
Found on impish/linux-azure: 5.13.0-1008.9 -- 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/1949532 Title: ubuntu_ltp_controllers tests failing on Impish Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Almost half of the ubuntu_ltp_controllers tests are failing due to the general pattern 'cgroup_name already mounted or mount point busy' causing the tests to fail. e.g. mount: /dev/cgroup: ltp_cgroup already mounted or mount point busy. cgroup_fj_function2_memory 1 TBROK: mount -t cgroup -o memory ltp_cgroup /dev/cgroup failed From investigation it seems there could be an issue with the transition to cgroup-v2. There have been rumors on the ltp mailing list that one of these days the tests could break due to the transition. Switching to cgroup-v2, likely due to a systemd update, could cause these tests to break due to different mount and cgroup hierarchy semantics. I could only reproduce a subset of the new failures we are seeing, but after setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, a lot of the failures I could produce went away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+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 1949532] Re: ubuntu_ltp_controllers tests failing on Impish
Found on impish/linux-aws: 5.13.0-1007.8 -- 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/1949532 Title: ubuntu_ltp_controllers tests failing on Impish Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Almost half of the ubuntu_ltp_controllers tests are failing due to the general pattern 'cgroup_name already mounted or mount point busy' causing the tests to fail. e.g. mount: /dev/cgroup: ltp_cgroup already mounted or mount point busy. cgroup_fj_function2_memory 1 TBROK: mount -t cgroup -o memory ltp_cgroup /dev/cgroup failed From investigation it seems there could be an issue with the transition to cgroup-v2. There have been rumors on the ltp mailing list that one of these days the tests could break due to the transition. Switching to cgroup-v2, likely due to a systemd update, could cause these tests to break due to different mount and cgroup hierarchy semantics. I could only reproduce a subset of the new failures we are seeing, but after setting systemd.unified_cgroup_hierarchy=0 on the kernel command line which sets cgroup back to v1, a lot of the failures I could produce went away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1949532/+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-gke-5.4/5.4.0.1056.59~18.04.21)
All autopkgtests for the newly accepted linux-meta-gke-5.4 (5.4.0.1056.59~18.04.21) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) systemd/237-3ubuntu10.52 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-gke-5.4 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951873] Re: Enable arm64 nitro enclaves
** Also affects: linux-aws (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Impish) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1951873 Title: Enable arm64 nitro enclaves Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Focal: New Status in linux-aws source package in Hirsute: New Status in linux-aws source package in Impish: New Bug description: SRU Justification [Impact] Enable arm64 support for Nitro Enclaves [Test Plan] Boot an AWS arm64 instance. Test for the existence of enclaves. [Where things could go wrong] Its possible this could affect amd64 enclave support. [Other Info] SF: #00323459 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1951873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951873] [NEW] Enable arm64 nitro enclaves
Public bug reported: SRU Justification [Impact] Enable arm64 support for Nitro Enclaves [Test Plan] Boot an AWS arm64 instance. Test for the existence of enclaves. [Where things could go wrong] Its possible this could affect amd64 enclave support. [Other Info] SF: #00323459 ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Tags: bot-stop-nagging ** Package changed: linux (Ubuntu) => linux-aws (Ubuntu) ** Tags added: bot-stop-nagging -- 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/1951873 Title: Enable arm64 nitro enclaves Status in linux-aws package in Ubuntu: New Bug description: SRU Justification [Impact] Enable arm64 support for Nitro Enclaves [Test Plan] Boot an AWS arm64 instance. Test for the existence of enclaves. [Where things could go wrong] Its possible this could affect amd64 enclave support. [Other Info] SF: #00323459 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1951873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950968] Re: v5.15 RT kernel fails to boot on some arm64 instances
The linux-modules-extra package is not a dependency for this kernel, which prevented installation of the qede module. I'll submit a patch to add extra as a dependency. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950968 Title: v5.15 RT kernel fails to boot on some arm64 instances Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: d2021.10.26/jammy/linux-realtime/5.15.0-1002.2 failed to boot on helo- kernel.arm64 without any logs. - Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.0-1002-realtime Found initrd image: /boot/initrd.img-5.15.0-1002-realtime Found linux image: /boot/vmlinuz-5.13.0-21-generic Found initrd image: /boot/initrd.img-5.13.0-21-generic done . Rebooting for installed Kernel meta package Traceback (most recent call last): File "/home/maas/ckct/sut-prep", line 187, in exit(app.main(args)) File "/home/maas/ckct/sut-prep", line 74, in main if instance.provision(): File "/home/maas/ckct/lib/target.py", line 1301, in provision s.reboot(progress=reboot) File "/home/maas/ckct/lib/target.py", line 621, in reboot s.wait_for_target() File "/home/maas/ckct/lib/target.py", line 173, in wait_for_target raise WaitForTarget(message) lib.target.WaitForTarget: The specified timeout (30 minutes) was reached while waiting for the target system (10.229.83.183) to come back up. WARNING - [2021-11-15 10:42:43.270713] ssh command (return): uname -vr (0) 5.13.0-21-generic #21-Ubuntu SMP Tue Oct 19 09:01:50 UTC 2021 - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1899690] Re: HWE Kernel causes incompatable behavior with Kubernetes
It looks like the version was iptables v1.8.3 according to my comment at [1] ``` root@kube-proxy:/# iptables-save --version iptables-save v1.8.3 (legacy) root@kube-proxy:/# ``` [1] https://github.com/kubernetes/kubernetes/issues/95409#issuecomment-706472275 ** Bug watch added: github.com/kubernetes/kubernetes/issues #95409 https://github.com/kubernetes/kubernetes/issues/95409 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1899690 Title: HWE Kernel causes incompatable behavior with Kubernetes Status in linux-meta-hwe-5.4 package in Ubuntu: New Bug description: This is a follow up from a bug that I filed for Kubernetes: https://github.com/kubernetes/kubernetes/issues/95409 **What happened**: I'm running Kubernetes on my Ubuntu 18.04 systems. Kubernetes is installed via Rancher (RKE). My Kubernetes 1.17 cluster (and Kubernetes 1.16 cluster) has 40-50 firewall rules that say `[unsupported revision]`. I am concerned this will cause problems with ``` # iptables-save ... -A KUBE-SEP-AAAREDACTED1 -s 10.99.99.27/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED1 -p tcp -m tcp -j DNAT [unsupported revision] -A KUBE-SEP-AAAREDACTED2 -s 10.99.99.40/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED2 -p tcp -m tcp -j DNAT [unsupported revision] -A KUBE-SEP-AAAREDACTED3 -s 10.99.99.27/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED3 -p tcp -m tcp -j DNAT [unsupported revision] ``` **What you expected to happen**: I expect these firewall rules to be valid, like so: ``` # iptables-save ... -A KUBE-SEP-AAAREDACTED1 -s 10.99.99.27/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED1 -p tcp -m tcp -j DNAT --to-destination 10.99.99.27:9153 -A KUBE-SEP-AAAREDACTED2 -s 10.99.99.40/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED2 -p tcp -m tcp -j DNAT --to-destination 10.99.99.40:3306 -A KUBE-SEP-AAAREDACTED3 -s 10.99.99.27/32 -j KUBE-MARK-MASQ -A KUBE-SEP-AAAREDACTED3 -p tcp -m tcp -j DNAT --to-destination 10.99.99.27:53 ``` **How to reproduce it (as minimally and precisely as possible)**: 1. Allocate a worker node 1. Install Ubuntu 18.04.5 2. Install Kubernetes with Canal * I'm using Rancher & RKE, and I assume this happens with vanilla versions of Kubernetes as well. 3. Install the Ubuntu LTS Hardware Enablement (HWE) kernel via https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Server 4. Reboot 5. When the system comes back online & Docker is running, look for invalid iptables rules as shown above. ** Environment ** - 18.04.5 LTS (Bionic Beaver) - Kernel - Linux cntest13 5.4.0-48-generic #52~18.04.1-Ubuntu SMP Thu Sep 10 12:50:22 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux\ - Kubernetes 1.17.11 - Installed via RKE - Canal version: rancher/calico-node:v3.13.4 (Not sure how to tell the other version numbers) - Docker version: 18.9.9 Happens with both Bare Metal and VM systems: - Bare metal nodes - AMD EPYC 7452 32-Core Processor, large memory, multiple NICs to different networks - VMs on VMware vSphere Default iptables version: ``` # iptables --version iptables v1.6.1 # ls -ld `which iptables` lrwxrwxrwx 1 root root 13 Nov 12 2017 /sbin/iptables -> xtables-multi # ``` ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-generic-hwe-18.04 5.4.0.48.52~18.04.42 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.18 Architecture: amd64 Date: Tue Oct 13 19:19:20 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.4/+bug/1899690/+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 1951868] Re: [amdgpu] USB4 support for DP tunneling
** Description changed: [Impact] - DP tunneling over USB4 requires additional work in the AMD GPU driver that isn't present in 5.14 or 5.15. The code will be submitted during the 5.16 kernel cycle and will need to be backported into 5.14 OEM kernel to support any programs that need it. + DP tunneling over USB4 requires additional work in the AMD GPU driver that isn't present in 5.14 or 5.15. The code is included in 5.16 kernel and will need to be backported into 5.14 OEM kernel (and jammy/5.15) to support any programs that need it. [Fix] - Cherry-pick/backport 30 commits from 5.16 to 5.15. - + Cherry-pick/backport 30 commits from 5.16 to 5.15. OEM-5.14 needs a few additional ones from 5.15. [Test case] WIP [Where things could go wrong] WIP -- 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/1951868 Title: [amdgpu] USB4 support for DP tunneling Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] DP tunneling over USB4 requires additional work in the AMD GPU driver that isn't present in 5.14 or 5.15. The code is included in 5.16 kernel and will need to be backported into 5.14 OEM kernel (and jammy/5.15) to support any programs that need it. [Fix] Cherry-pick/backport 30 commits from 5.16 to 5.15. OEM-5.14 needs a few additional ones from 5.15. [Test case] WIP [Where things could go wrong] WIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951868/+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 1951868] 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 1951868 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/1951868 Title: [amdgpu] USB4 support for DP tunneling Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] DP tunneling over USB4 requires additional work in the AMD GPU driver that isn't present in 5.14 or 5.15. The code will be submitted during the 5.16 kernel cycle and will need to be backported into 5.14 OEM kernel to support any programs that need it. [Fix] Cherry-pick/backport 30 commits from 5.16 to 5.15. [Test case] WIP [Where things could go wrong] WIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951868/+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 1951868] [NEW] [amdgpu] USB4 support for DP tunneling
Public bug reported: [Impact] DP tunneling over USB4 requires additional work in the AMD GPU driver that isn't present in 5.14 or 5.15. The code will be submitted during the 5.16 kernel cycle and will need to be backported into 5.14 OEM kernel to support any programs that need it. [Fix] Cherry-pick/backport 30 commits from 5.16 to 5.15. [Test case] WIP [Where things could go wrong] WIP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) 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/1951868 Title: [amdgpu] USB4 support for DP tunneling Status in linux package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] DP tunneling over USB4 requires additional work in the AMD GPU driver that isn't present in 5.14 or 5.15. The code will be submitted during the 5.16 kernel cycle and will need to be backported into 5.14 OEM kernel to support any programs that need it. [Fix] Cherry-pick/backport 30 commits from 5.16 to 5.15. [Test case] WIP [Where things could go wrong] WIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951868/+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 1946672] Re: Enable multicast in the "kvm" kernels
** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-kvm (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1946672 Title: Enable multicast in the "kvm" kernels Status in cloud-images: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Focal: Fix Committed Bug description: I work in the OpenStack Neutron project and recently I wanted to optimize our CI scenario jobs by using Ubuntu minimal image as guest image for some tests (see patch https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/813195) Unfortunately it seems that there is problem with one multicast scenario test while using ubuntu-minimal image (https://cloud-images.ubuntu.com/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img). The problem is that VM booted from that image don't subscribes properly to the IGMP multicast group thus test is failing. All works fine when image https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img is used in the same test. The problem is that in the minimal image kernel linux-image-kvm (vs. linux-image-generic in the "regular" cloud image) and that "-kvm" image has disabled MULTICAST: # CONFIG_IP_MULTICAST is not set Would it be maybe possible to enable this option in the kernel used in the "minimal" cloud images? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1946672/+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 1950584] Re: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
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/1950584
Title:
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and
offline
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
"Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
->adjust_perf() callback") caused intel_pstate to use nonzero HWP
desired values in certain usage scenarios, but it did not prevent
them from being leaked into the confugirations in which HWP desired
is expected to be 0"
I believe I'm seeing this issue on my laptop during suspend/resume.
The upstream fix is:
[Fix]
commit dbea75fe18f60e364de6d994fc938a24ba249d81
Author: Rafael J. Wysocki
Date: Wed Nov 3 19:43:47 2021 +0100
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: cking 2316 F pulseaudio
/dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
/dev/snd/controlC0: cking 2316 F pulseaudio
/dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-06-07 (156 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210607)
MachineType: LENOVO 20L5CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
RelatedPackageVersions:
linux-restricted-modules-5.13.0-20-generic N/A
linux-backports-modules-5.13.0-20-generic N/A
linux-firmware 1.202
Tags: jammy
Uname: Linux 5.13.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
vboxusers
_MarkForUpload: True
dmi.bios.date: 01/11/2020
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET55W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.20
dmi.modalias:
dmi:bvnLENOVO:bvrN24ET55W(1.30):bd01/11/2020:br1.30:efr1.20:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950584/+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 1951866] [NEW] BUILD & CLEAN scripts should support DESTDIR option
Public bug reported: BUILD & CLEAN scripts should support DESTDIR option When paths are mangled in the BUILD & CLEAN scripts it would be nice if it injected DESTDIR variable support. Such that one could BUILD/CLEAN modules in a different target directory when the bits directory is read only. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1951866 Title: BUILD & CLEAN scripts should support DESTDIR option Status in linux-restricted-modules package in Ubuntu: New Bug description: BUILD & CLEAN scripts should support DESTDIR option When paths are mangled in the BUILD & CLEAN scripts it would be nice if it injected DESTDIR variable support. Such that one could BUILD/CLEAN modules in a different target directory when the bits directory is read only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1951866/+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 1947206] Re: Updates to ib_peer_memory requested by Nvidia
** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947206 Title: Updates to ib_peer_memory requested by Nvidia Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Bug description: [Impact] Nvidia notified me via private email that they'd discovered some issues with the ib_peer_memory patch we are carrying in hirsute/impish and sent me a patch intended to resolve them. My knowledge of these changes is limited to what is mentioned in the commit message: - Allow clients to opt out of unmap during invalidation - Fix some bugs in the sequencing of mlx5 MRs - Enable ATS for peer memory [Test Case] ib_write_bw from the perftest package, rebuilt with CUDA support, can be used as a smoke test of this feature. I'll attach a sample test script here. I've verified this test passes with the kernels in the archive, and continues to pass with the provided patch applied. [Fix] Nvidia has emailed me fixes for both trees. They are not currently available in a public tree elsewhere, though I'm told at some point they should end up in a branch here: https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/ [What could go wrong] The only known use case for ib_peer_memory are Nvidia GPU users making use of the GPU PeerDirect feature where GPUs can share memory with one another over an Infiniband network. Bugs here could cause problems (hangs, crashes, corruption) with such workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947206/+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 1951865] [NEW] nvidia modules not stripped before signing like everything else
Public bug reported: Ubuntu kernel modules are stripped prior to signing: $(build_cd) $(kmake) $(build_O) $(conc_level) modules_install $(vdso) \ INSTALL_MOD_STRIP=1 INSTALL_MOD_PATH=$(pkgdir)/ \ INSTALL_FW_PATH=$(pkgdir)/lib/firmware/$(abi_release)-$* And STRIPPING in the buildlog. But when doing the build of the nvidia dkms modules, they are not stripped prior to signing: # sh ./BUILD unsigned # cp *.ko unstripped/ # cp -r unstripped stripped # cd stripped; strip --strip-debug *.ko; cd ../ # du --si unstripped/ stripped/ 99M unstripped/ 46M stripped/ # du --si unstripped/*.ko stripped/*.ko 3.9Munstripped/nvidia-drm.ko 2.3Munstripped/nvidia-modeset.ko 316kunstripped/nvidia-peermem.ko 41M unstripped/nvidia-uvm.ko 51M unstripped/nvidia.ko 103kstripped/nvidia-drm.ko 1.6Mstripped/nvidia-modeset.ko 17k stripped/nvidia-peermem.ko 1.7Mstripped/nvidia-uvm.ko 43M stripped/nvidia.ko I am unsure how come DKMS doesn't call install modules with INSTALL_MOD_STRIP=1 option, and if stripping nvidia modules results in correctly working drivers. If it is possible to strip nvidia modules, they will half in size. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1951865 Title: nvidia modules not stripped before signing like everything else Status in linux-restricted-modules package in Ubuntu: New Bug description: Ubuntu kernel modules are stripped prior to signing: $(build_cd) $(kmake) $(build_O) $(conc_level) modules_install $(vdso) \ INSTALL_MOD_STRIP=1 INSTALL_MOD_PATH=$(pkgdir)/ \ INSTALL_FW_PATH=$(pkgdir)/lib/firmware/$(abi_release)-$* And STRIPPING in the buildlog. But when doing the build of the nvidia dkms modules, they are not stripped prior to signing: # sh ./BUILD unsigned # cp *.ko unstripped/ # cp -r unstripped stripped # cd stripped; strip --strip-debug *.ko; cd ../ # du --si unstripped/ stripped/ 99M unstripped/ 46M stripped/ # du --si unstripped/*.ko stripped/*.ko 3.9M unstripped/nvidia-drm.ko 2.3M unstripped/nvidia-modeset.ko 316k unstripped/nvidia-peermem.ko 41M unstripped/nvidia-uvm.ko 51M unstripped/nvidia.ko 103k stripped/nvidia-drm.ko 1.6M stripped/nvidia-modeset.ko 17k stripped/nvidia-peermem.ko 1.7M stripped/nvidia-uvm.ko 43M stripped/nvidia.ko I am unsure how come DKMS doesn't call install modules with INSTALL_MOD_STRIP=1 option, and if stripping nvidia modules results in correctly working drivers. If it is possible to strip nvidia modules, they will half in size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1951865/+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 1950584] Re: cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1950584
Title:
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and
offline
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Bug description:
[Impact]
"Commit a365ab6b9dfb ("cpufreq: intel_pstate: Implement the
->adjust_perf() callback") caused intel_pstate to use nonzero HWP
desired values in certain usage scenarios, but it did not prevent
them from being leaked into the confugirations in which HWP desired
is expected to be 0"
I believe I'm seeing this issue on my laptop during suspend/resume.
The upstream fix is:
[Fix]
commit dbea75fe18f60e364de6d994fc938a24ba249d81
Author: Rafael J. Wysocki
Date: Wed Nov 3 19:43:47 2021 +0100
cpufreq: intel_pstate: Clear HWP desired on suspend/shutdown and offline
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: cking 2316 F pulseaudio
/dev/snd/pcmC1D0c: cking 2316 F...m pulseaudio
/dev/snd/controlC0: cking 2316 F pulseaudio
/dev/snd/pcmC0D0p: cking 2316 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2021-06-07 (156 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210607)
MachineType: LENOVO 20L5CTO1WW
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-20-generic
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
RelatedPackageVersions:
linux-restricted-modules-5.13.0-20-generic N/A
linux-backports-modules-5.13.0-20-generic N/A
linux-firmware 1.202
Tags: jammy
Uname: Linux 5.13.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
vboxusers
_MarkForUpload: True
dmi.bios.date: 01/11/2020
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N24ET55W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L5CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.20
dmi.modalias:
dmi:bvnLENOVO:bvrN24ET55W(1.30):bd01/11/2020:br1.30:efr1.20:svnLENOVO:pn20L5CTO1WW:pvrThinkPadT480:skuLENOVO_MT_20L5_BU_Think_FM_ThinkPadT480:rvnLENOVO:rn20L5CTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480
dmi.product.name: 20L5CTO1WW
dmi.product.sku: LENOVO_MT_20L5_BU_Think_FM_ThinkPad T480
dmi.product.version: ThinkPad T480
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950584/+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 1951862] [NEW] nv-interface is linked but not needed
Public bug reported: grep nv-interface.o -r . ./CLEAN:rm -f nvidia/nv-interface.o ./BUILD:/usr/bin/ld.bfd -r -o nvidia/nv-interface.o nvidia/nv.o nvidia/nv-pci.o nvidia/nv-acpi.o nvidia/nv-cray.o nvidia/nv-dma.o nvidia/nv-i2c.o nvidia/nv-mmap.o nvidia/nv-p2p.o nvidia/nv-pat.o nvidia/nv-procfs.o nvidia/nv-procfs-utils.o nvidia/nv-usermap.o nvidia/nv-vm.o nvidia/nv-vtophys.o nvidia/os-interface.o nvidia/os-mlock.o nvidia/os-pci.o nvidia/os-registry.o nvidia/os-usermap.o nvidia/nv-modeset-interface.o nvidia/nv-pci-table.o nvidia/nv-kthread-q.o nvidia/nv-memdbg.o nvidia/nv-ibmnpu.o nvidia/nv-report-err.o nvidia/nv-rsync.o nvidia/nv-msi.o nvidia/nv-caps.o nvidia/nv-frontend.o nvidia/nv_uvm_interface.o nvidia/nvlink_linux.o nvidia/nvlink_caps.o nvidia/linux_nvswitch.o nvidia/procfs_nvswitch.o nvidia/i2c_nvswitch.o Note that nvidia/nv-interface.o is created, but not used by any modules. In the kbuild we have: # # Build nv-interface.o from the kernel interface layer objects, suitable # for further processing by the top-level makefile to produce a precompiled # kernel interface file. # NVIDIA_INTERFACE := nvidia/nv-interface.o # Linux kernel v5.12 and later looks at "always-y", Linux kernel versions # before v5.6 looks at "always"; kernel versions between v5.12 and v5.6 # look at both. always += $(NVIDIA_INTERFACE) always-y += $(NVIDIA_INTERFACE) $(obj)/$(NVIDIA_INTERFACE): $(addprefix $(obj)/,$(NVIDIA_OBJECTS)) $(LD) -r -o $@ $^ But i'm not sure if we actually do any further processing, or use precompiled kernel interface file. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Description changed: grep nv-interface.o -r . ./CLEAN:rm -f nvidia/nv-interface.o ./BUILD:/usr/bin/ld.bfd -r -o nvidia/nv-interface.o nvidia/nv.o nvidia/nv-pci.o nvidia/nv-acpi.o nvidia/nv-cray.o nvidia/nv-dma.o nvidia/nv-i2c.o nvidia/nv-mmap.o nvidia/nv-p2p.o nvidia/nv-pat.o nvidia/nv-procfs.o nvidia/nv-procfs-utils.o nvidia/nv-usermap.o nvidia/nv-vm.o nvidia/nv-vtophys.o nvidia/os-interface.o nvidia/os-mlock.o nvidia/os-pci.o nvidia/os-registry.o nvidia/os-usermap.o nvidia/nv-modeset-interface.o nvidia/nv-pci-table.o nvidia/nv-kthread-q.o nvidia/nv-memdbg.o nvidia/nv-ibmnpu.o nvidia/nv-report-err.o nvidia/nv-rsync.o nvidia/nv-msi.o nvidia/nv-caps.o nvidia/nv-frontend.o nvidia/nv_uvm_interface.o nvidia/nvlink_linux.o nvidia/nvlink_caps.o nvidia/linux_nvswitch.o nvidia/procfs_nvswitch.o nvidia/i2c_nvswitch.o Note that nvidia/nv-interface.o is created, but not used by any modules. + + In the kbuild we have: + + # + # Build nv-interface.o from the kernel interface layer objects, suitable + # for further processing by the top-level makefile to produce a precompiled + # kernel interface file. + # + + NVIDIA_INTERFACE := nvidia/nv-interface.o + + # Linux kernel v5.12 and later looks at "always-y", Linux kernel versions + # before v5.6 looks at "always"; kernel versions between v5.12 and v5.6 + # look at both. + + always += $(NVIDIA_INTERFACE) + always-y += $(NVIDIA_INTERFACE) + + $(obj)/$(NVIDIA_INTERFACE): $(addprefix $(obj)/,$(NVIDIA_OBJECTS)) + $(LD) -r -o $@ $^ + + But i'm not sure if we actually do any further processing, or use + precompiled kernel interface file. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1951862 Title: nv-interface is linked but not needed Status in linux-restricted-modules package in Ubuntu: New Bug description: grep nv-interface.o -r . ./CLEAN:rm -f nvidia/nv-interface.o ./BUILD:/usr/bin/ld.bfd -r -o nvidia/nv-interface.o nvidia/nv.o nvidia/nv-pci.o nvidia/nv-acpi.o nvidia/nv-cray.o nvidia/nv-dma.o nvidia/nv-i2c.o nvidia/nv-mmap.o nvidia/nv-p2p.o nvidia/nv-pat.o nvidia/nv-procfs.o nvidia/nv-procfs-utils.o nvidia/nv-usermap.o nvidia/nv-vm.o nvidia/nv-vtophys.o nvidia/os-interface.o nvidia/os-mlock.o nvidia/os-pci.o nvidia/os-registry.o nvidia/os-usermap.o nvidia/nv-modeset-interface.o nvidia/nv-pci-table.o nvidia/nv-kthread-q.o nvidia/nv-memdbg.o nvidia/nv-ibmnpu.o nvidia/nv-report-err.o nvidia/nv-rsync.o nvidia/nv-msi.o nvidia/nv-caps.o nvidia/nv-frontend.o nvidia/nv_uvm_interface.o nvidia/nvlink_linux.o nvidia/nvlink_caps.o nvidia/linux_nvswitch.o nvidia/procfs_nvswitch.o nvidia/i2c_nvswitch.o Note that nvidia/nv-interface.o is created, but not used by any modules. In the kbuild we have: # # Build nv-interface.o from the kernel interface layer objects, suitable # for further processing by the top-level makefile to produce a precompiled # kernel interface file. # NVIDIA_INTERFACE := nvidia/nv-interface.o # Linux kernel v5.12 and later looks at "always-y", Linux kernel versions # before v5.6 looks at "always"; kernel versions between v5.12 and v5.6 # look at both. always += $(NVIDIA_INTERFACE) always-y +=
[Kernel-packages] [Bug 1950536] Re: keyboard not working on Medion notebook s17 series
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950536 Title: keyboard not working on Medion notebook s17 series Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: [Impact] The keyboard of some medion s17 series laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. This is a bug similar to #1909814. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950536/+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 1950144] Re: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm)
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950144 Title: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm) Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * The kernel is unable to read partitions on virtio-block DASD (on KVM). That's a severe situation, since it prevents Ubuntu from starting, if installed on a DASD. This issue can either occur after a fresh installation or after an upgrade. * The virtio specification virtio-v1.1-cs01 states: "Transitional devices MUST detect Legacy drivers by detecting that VIRTIO_F_VERSION_1 has not been acknowledged by the driver." And this is what QEMU as of 6.1 has done relying solely on VIRTIO_F_VERSION_1 for detecting that. * But the specification also says: "... the driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device ..." before setting FEATURES_OK. * In this case, any transitional device relying solely on VIRTIO_F_VERSION_1 for detecting legacy drivers will return data in legacy format. In particular, this implies that it's in big endian format for big endian guests. This naturally confuses the driver that expects little endian in the modern mode. * VIRTIO_F_VERSION_1 can only be relied on after the feature negotiation is done. * 'verify' is called before virtio_finalize_features(), so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. * For QEMU, we can work around the issue by writing out the feature bits with VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for this. This isn't enough to address all vhost devices since these do not get the features until FEATURES_OK, however it looks like the affected devices actually never handled the endianness for legacy mode correctly, so at least that's not a regression. [Fix] * 2f9a174f918e29608564c7a4e8329893ab604fb4 2f9a174f918e "virtio: write back F_VERSION_1 before validate" [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server 20.04 as KVM host. * This Ubuntu KVM host can either be installed on FCP or DASD storage, but at least one DASD disk need to be reserved for a KVM guest. * Now hand over the reserved DASD disk (low-level formatted using dasdfmt and partitioned using fdasd) using 'virtio-block' to a KVM virtual machine (e.g. using a virsh VM config). * Try to install an Ubuntu KVM virtual machine using this DASD disk, that includes the check and read of the partition table. [Where problems could occur] * First of all requested commit contains one additional if statement; and is due tothat relatively traceable. * But the change is in /drivers/virtio/virtio.c, means in common code! * This issue obviously affects big endian systems only. * But if done wrong, it may effect in worst-case little endian systems, too! * But the if statement explicitly checks for '!virtio_legacy_is_little_endian()'. * Only virtio net and virtio blk devices seem to be affected. * And the commit/solutions was in-depth discussed upstream here: https://lore.kernel.org/all/20211011053921.1198936-1-pa...@linux.ibm.com/t/#u [Other] * Patches are upstream accepted with since 5.15-rc6 and tagged for upstream stable #v4.11. Hence jammy is not affected. * Request was to add the patches to focal / 20.04, but to avoid potential regressions on upgrades, the patches need to be added to impish and hirsute, too. * Fortunately cherry-picking the commit works cleanly from all the affected Ubuntu releases. __ Description: kernel: unable to read partitions on virtio-block dasd (kvm) Symptom: unable to read partitions on virtio-block dasd (kvm) Problem: verify is called before virtio_finalize_features() , so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. Solution: For QEMU, we can work around the issue by
[Kernel-packages] [Bug 1951861] [NEW] Fix non-working e1000e device after resume
Public bug reported: [Impact] e1000e devices stop working after s2idle resume. [Fix] Revert the offending patch series, which is to bring some minor power saving. [Test] Vendor did extensive tests and didn't find any regression, and the power consumption remains the same. [Where problems could occur] Maybe on some system the series can save some energy, so reverting will cause some power consumption increase. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Status: Confirmed ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: High Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: High Status: Confirmed ** Affects: linux (Ubuntu Impish) Importance: High Status: Confirmed ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1938506 somerville ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.13 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: Confirmed => Invalid ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Tags added: oem-priority originate-from-1938506 somerville -- 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/1951861 Title: Fix non-working e1000e device after resume Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] e1000e devices stop working after s2idle resume. [Fix] Revert the offending patch series, which is to bring some minor power saving. [Test] Vendor did extensive tests and didn't find any regression, and the power consumption remains the same. [Where problems could occur] Maybe on some system the series can save some energy, so reverting will cause some power consumption increase. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950144] Re: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm)
** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950144 Title: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm) Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * The kernel is unable to read partitions on virtio-block DASD (on KVM). That's a severe situation, since it prevents Ubuntu from starting, if installed on a DASD. This issue can either occur after a fresh installation or after an upgrade. * The virtio specification virtio-v1.1-cs01 states: "Transitional devices MUST detect Legacy drivers by detecting that VIRTIO_F_VERSION_1 has not been acknowledged by the driver." And this is what QEMU as of 6.1 has done relying solely on VIRTIO_F_VERSION_1 for detecting that. * But the specification also says: "... the driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device ..." before setting FEATURES_OK. * In this case, any transitional device relying solely on VIRTIO_F_VERSION_1 for detecting legacy drivers will return data in legacy format. In particular, this implies that it's in big endian format for big endian guests. This naturally confuses the driver that expects little endian in the modern mode. * VIRTIO_F_VERSION_1 can only be relied on after the feature negotiation is done. * 'verify' is called before virtio_finalize_features(), so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. * For QEMU, we can work around the issue by writing out the feature bits with VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for this. This isn't enough to address all vhost devices since these do not get the features until FEATURES_OK, however it looks like the affected devices actually never handled the endianness for legacy mode correctly, so at least that's not a regression. [Fix] * 2f9a174f918e29608564c7a4e8329893ab604fb4 2f9a174f918e "virtio: write back F_VERSION_1 before validate" [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server 20.04 as KVM host. * This Ubuntu KVM host can either be installed on FCP or DASD storage, but at least one DASD disk need to be reserved for a KVM guest. * Now hand over the reserved DASD disk (low-level formatted using dasdfmt and partitioned using fdasd) using 'virtio-block' to a KVM virtual machine (e.g. using a virsh VM config). * Try to install an Ubuntu KVM virtual machine using this DASD disk, that includes the check and read of the partition table. [Where problems could occur] * First of all requested commit contains one additional if statement; and is due tothat relatively traceable. * But the change is in /drivers/virtio/virtio.c, means in common code! * This issue obviously affects big endian systems only. * But if done wrong, it may effect in worst-case little endian systems, too! * But the if statement explicitly checks for '!virtio_legacy_is_little_endian()'. * Only virtio net and virtio blk devices seem to be affected. * And the commit/solutions was in-depth discussed upstream here: https://lore.kernel.org/all/20211011053921.1198936-1-pa...@linux.ibm.com/t/#u [Other] * Patches are upstream accepted with since 5.15-rc6 and tagged for upstream stable #v4.11. Hence jammy is not affected. * Request was to add the patches to focal / 20.04, but to avoid potential regressions on upgrades, the patches need to be added to impish and hirsute, too. * Fortunately cherry-picking the commit works cleanly from all the affected Ubuntu releases. __ Description: kernel: unable to read partitions on virtio-block dasd (kvm) Symptom: unable to read partitions on virtio-block dasd (kvm) Problem: verify is called before
[Kernel-packages] [Bug 1950042] Re: Let NVMe with HMB use native power control again
** Changed in: linux (Ubuntu Impish) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950042 Title: Let NVMe with HMB use native power control again Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Confirmed Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: Impact] NVMe with HMB may still do DMA during suspend, so there was a commit that put the NVMe to PCI D3 during suspend to prevent DMA activities. However, this makes them consumes much more power because modern NVMe requires to stay at PCI D0 to make its natve power control work. [Fix] Instead of put the NVMe to PCI D3 and reset it afterward, simply disable HMB and re-enable HMB, for suspend and resume respectively. [Test] On affected system, Intel SoC can only reach PC3 during suspend. With the SRU applied, the Intel SoC can reach PC10 and SLP_S0 and use significant less power. [Where problems could occur] The original approach, i.e. disable NVMe and put it to PCI D3 to prevent DMA activies, was just a precaution. There wasn't any case that indicates it happens in practice. This is a different approach to the same problem, which is a theoretical problem. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950042/+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 1950239] Re: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS
** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) 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/1950239 Title: creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve failed with XFS Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] setgid files may be created on setgid directories owned by the directory group by users not belonging to that group. That is restricted to XFS. [Fix/Backport] The fix for 5.11 and 5.10 kernels is one simple commit with a minor backport conflict fixup on 5.10. 5.4, on the other hand, required other 3 pre-requisites, which could be picked cleanly. On 4.15, however, they needed a lot of mangling and fixes. [Test case] creat09 LTP test case. [Potential regression] The creation of files on XFS may have the wrong attributes. Also, on 5.4 and 4.15, the potential regression is larger, also affecting quota, statistics and other interfaces where uid, gid and projid are exposed. = These two tests, creat09 from ubuntu_ltp_syscalls and cve-2018-13405 from ubuntu_ltp/cve are actually the same test. Issue found on F-oem-5.10.0-1051.53 With LTP upstream head SHA1 2ac54d426 This is not a regression, it's because of a recent update that enables this test on different filesystems: https://github.com/linux-test-project/ltp/commit/433b6cf7ade3d5e3bd4b85ac89b164c53312e65a Test failed on XFS with: tst_test.c:1431: TINFO: Testing on xfs tst_test.c:932: TINFO: Formatting /dev/loop3 with xfs opts='' extra opts='' tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s creat09.c:55: TINFO: User nobody: uid = 65534, gid = 65534 creat09.c:57: TINFO: Found unused GID 11: SUCCESS (0) creat09.c:88: TPASS: mntpoint/testdir/creat.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/creat.tmp: Setgid bit is set creat09.c:88: TPASS: mntpoint/testdir/open.tmp: Owned by correct group creat09.c:92: TFAIL: mntpoint/testdir/open.tmp: Setgid bit is set Test log: Checking for required user/group ids 'nobody' user id and group found. 'bin' user id and group found. 'daemon' user id and group found. Users group found. Sys group found. Required users/groups exist. no big block device was specified on commandline. Tests which require a big block device are disabled. You can specify it with option -z INFO: Test start time: Mon Nov 8 10:00:06 UTC 2021 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 61758 -n 61758 -f /tmp/ltp-shLYORuoRT/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_device.c:88: TINFO: Found free device 3 '/dev/loop3' tst_supported_fs_types.c:88: TINFO: Kernel supports ext2 tst_supported_fs_types.c:50: TINFO: mkfs.ext2 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext3 tst_supported_fs_types.c:50: TINFO: mkfs.ext3 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports ext4 tst_supported_fs_types.c:50: TINFO: mkfs.ext4 does exist tst_supported_fs_types.c:88: TINFO: Kernel supports xfs tst_supported_fs_types.c:50: TINFO: mkfs.xfs does exist tst_supported_fs_types.c:88: TINFO: Kernel supports btrfs tst_supported_fs_types.c:50: TINFO: mkfs.btrfs does exist tst_supported_fs_types.c:146: TINFO: Skipping vfat as requested by the test tst_supported_fs_types.c:146: TINFO: Skipping exfat as requested by the test tst_supported_fs_types.c:88: TINFO: Kernel supports tmpfs
[Kernel-packages] [Bug 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing
Kernel 5.16 on Ubuntu 21.10 have this driver! https://sypalo.com/how-to-upgrade-ubuntu Worked for me on Lenovo Legion 5. -- 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/1945967 Title: rtw89 kernel module for Realtek 8852 wifi is missing Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Confirmed Bug description: == SRU Justification == [Impact] Realtek 8852AE, which is used by many new laptops, doesn't have a driver. [Fix] Add rtw89 driver to support Realtek 8852AE. [Test] After applying the patch, 8852AE can scan, connect and do TX/RX. [Where problems could occur] This is a brand new driver, unless the driver hits some subtle PCI or IOMMU bugs, there isn't much chance to introduce any regression. == Original Bug Report == Hi, Resulting: no wifi adapter detected. Currently WIP: https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=* Workaround: use https://github.com/lwfinger/rtw89 that allows to build a dkms deb package. Ubuntu Impish kernel 5.13 (or 5.15 from unstable ppa) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-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: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945967/+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 1950644] Re: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) 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/1950644 Title: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Some uses of kernel_read_file_from_fd may lead to a WARN when the file is not opened for reading. The WARNING, however, is not present on earlier kernels, which will return a different error code. The fix, however, has been applied to upstream stable and may be worth so tests can PASS without much change. [Fix/Backport] The fix is trivial, but the backport for Focal and Bionic was picked up from 5.4.y upstream stable tree, because the function was moved to a different file. [Test case] The finit_module02 test case from LTP covers this. [Potential regression] kernel_read_file_from_fd is used for module loading and kexec, so there is where regressions might show up. = ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure (5.4.0-1064.67): tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+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 1950644] Re: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels
** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950644 Title: ubuntu_ltp / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Some uses of kernel_read_file_from_fd may lead to a WARN when the file is not opened for reading. The WARNING, however, is not present on earlier kernels, which will return a different error code. The fix, however, has been applied to upstream stable and may be worth so tests can PASS without much change. [Fix/Backport] The fix is trivial, but the backport for Focal and Bionic was picked up from 5.4.y upstream stable tree, because the function was moved to a different file. [Test case] The finit_module02 test case from LTP covers this. [Potential regression] kernel_read_file_from_fd is used for module loading and kexec, so there is where regressions might show up. = ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure (5.4.0-1064.67): tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+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 1867570] Re: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867570 Title: reuseport_bpf_numa in net from ubuntu_kernel_selftests fails on ppc64le Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Committed 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: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [ Impact ] The reuseport_bpf_numa testcase in selftests/net fails on some PowerPC systems with: # selftests: net: reuseport_bpf_numa # IPv4 UDP # send node 0, receive socket 0 # libnuma: Warning: Cannot read node cpumask from sysfs # ./reuseport_bpf_numa: failed to pin to node: No such file or directory not ok 3 selftests: net: reuseport_bpf_numa # exit=1 [ Fix ] In some platforms the numa node numbers are not necessarily consecutive, so when reuseport_bpf_numa iterates on the nodes from 0 to the max available node some of those will not be available. The fix is to change the testcase so it checks whether the node is available before trying to send/receive from it. [ Test ] Run reuseport_bpf_numa from selftests/net in one of the affected test nodes. [ Where Problems Could Occur ] This is a very simple fix which relies on the libnuma exported functions and bitmaps to check whether a numa node number is available on the system. If something is not right on how this check is made or on the libnuma code itself only the reuseport_bpf_numa testcase will be affected by reporting false negatives or having a reduced test coverage. [ Original bug report ] This issue was extracted from the comment in bug 1812638, since that bug will be specific for i386 This reuseport_bpf_numa in net will fail on PowerPC with: The output on B-5.3 P8 is: # selftests: net: reuseport_bpf_numa # IPv4 UDP # send node 0, receive socket 0 # send node 1, receive socket 7 # ./reuseport_bpf_numa: node id/receive socket mismatch not ok 3 selftests: net: reuseport_bpf_numa # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1867570/+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 1690085]
https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08DD658R3 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08DD5HTL6 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08DD5J6QW https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08DD4JM3G https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4SZYP1 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4VCVKG https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4VGNVP https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4T886X https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4VXHVH https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4VJ4X8 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4VNWZM https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4TTDCM https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B0989GD7LN https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B0989BWS5G https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B09895GGQ3 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B0989CP2JW https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DZ28NL https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DVRCJV https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DVF4M3 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DX8FX9 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07TZ8B4QH https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07TVXPMDF https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07TVXPMDH https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07TZ89NYS https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07TZ89NYS https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07WY58VXN https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07WSYP624 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07WTZ5BZB https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07WNZ1QBS https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07WNZ1QBS https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4TYZ8X https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4VM3XQ https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4VFQM4 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4V7ZPQ https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4TQ7CN https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4W5B4G https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4VN4PS https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4V2LBB https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08DD58ZJV https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08DD63Q1R https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08DD4MJT8 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08DC71VXH https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DWY1HW https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DYMKZ7 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DVH1H1 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DXJKH8 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099F1HR2G https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DSVP56 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DSWQBG https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DXDS8L https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DSDZ7G https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DYL6NS https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DXMR86 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B099DY86WR https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07TY4F5H2 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07TY4DVYX https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07TSSH1W1 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07TSSH1W2 https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08DD54X7X https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08DD4SLTC https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08DD4PJFJ https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08DD4XFJP https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4TZXQL https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4VPNZF https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4TTVKL https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B08B4V923P https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07WJZYVHH https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07WJZYV5C https://www.amazon.com/Alelly-Womens-Summer-Ruffle-Floral/dp/B07TVXNKGW
[Kernel-packages] [Bug 1690085]
https://www.alelly.net/ https://www.alelly.net/collections/dresses/products/layered-ruffled-open-back-puff-sleeve-swiss-dot-mini-dress-1 https://www.alelly.net/collections/dresses/products/leopard-printed-o-neck-short-sleeve-dress-11 https://www.alelly.net/collections/dresses/products/square-neck-puff-sleeve-babydoll-style-short-dress-12 https://www.alelly.net/collections/dresses/products/spaghetti-straps-jacquard-ruffle-mini-dress-4 https://www.alelly.net/collections/dresses/products/loose-fit-ruffled-color-block-dress-3 https://www.alelly.net/collections/dresses/products/swiss-dot-long-sleeve-mini-dress-with-waist-tie-2 https://www.alelly.net/collections/dresses/products/spaghetti-straps-v-neck-smocked-swing-floral-dress-3 https://www.alelly.net/collections/dresses/products/v-neck-lace-shoulder-sleeveless-mini-dress-3 https://www.alelly.net/collections/dresses/products/brief-comfy-pleated-long-sleeve-white-mini-dress https://www.alelly.net/collections/dresses/products/cold-shoulder-twist-knit-mini-dress-1 https://www.alelly.net/collections/dresses/products/v-neck-batwing-sleeve-maxi-dress https://www.alelly.net/collections/dresses/products/v-neck-split-sleeve-sequin-dress-with-slit https://www.alelly.net/collections/dresses/products/off-shoulder-lace-bodice-high-waist-maxi-skirt-evening-dress https://www.alelly.net/collections/dresses/products/floral-square-neck-ruffles-backless-a-line-short-dress https://www.alelly.net/collections/dresses/products/spaghetti-straps-silk-like-ruched-mini-dress https://www.alelly.net/collections/dresses/products/ruffled-off-shoulder-floral-dress https://www.alelly.net/collections/dresses/products/halloween-pumpkin-letter-print-striped-raglan-long-sleeve-mini-dress https://www.alelly.net/collections/dresses/products/crew-neck-twist-hollow-out-t-shirt-mini-dress-with-ruched-detail https://www.alelly.net/collections/dresses/products/asymmetric-cold-shoulder-denim-dress https://www.alelly.net/collections/dresses/products/velvet-puff-sleeve-mini-dress https://www.alelly.net/collections/dresses/products/leopard-print-spaghetti-strap-bodycon-mini-dress https://www.alelly.net/collections/dresses/products/wrap-v-neck-long-sleeve-ruched-velvet-mini-dress https://www.alelly.net/collections/dresses/products/pocket-lace-up-drawstring-hooded-mini-dress https://www.alelly.net/collections/dresses/products/plaid-striped-splicing-raglan-sleeve-mini-dress https://www.alelly.net/collections/dresses/products/layered-ruffled-open-back-puff-sleeve-swiss-dot-mini-dress-1 https://www.alelly.net/collections/dresses/products/leopard-printed-o-neck-short-sleeve-dress-11 https://www.alelly.net/collections/dresses/products/square-neck-puff-sleeve-babydoll-style-short-dress-12 https://www.alelly.net/collections/dresses/products/spaghetti-straps-jacquard-ruffle-mini-dress-4 https://www.alelly.net/collections/dresses/products/loose-fit-ruffled-color-block-dress-3 https://www.alelly.net/collections/dresses/products/swiss-dot-long-sleeve-mini-dress-with-waist-tie-2 https://www.alelly.net/collections/dresses/products/spaghetti-straps-v-neck-smocked-swing-floral-dress-3 https://www.alelly.net/collections/dresses/products/v-neck-lace-shoulder-sleeveless-mini-dress-3 https://www.alelly.net/collections/dresses/products/brief-comfy-pleated-long-sleeve-white-mini-dress https://www.alelly.net/collections/dresses/products/loose-fit-ruffled-color-block-dress-3 https://www.alelly.net/collections/dresses/products/swiss-dot-long-sleeve-mini-dress-with-waist-tie-2 https://www.alelly.net/collections/dresses/products/spaghetti-straps-v-neck-smocked-swing-floral-dress-3 https://www.alelly.net/collections/dresses/products/v-neck-lace-shoulder-sleeveless-mini-dress-3 https://www.alelly.net/collections/dresses/products/brief-comfy-pleated-long-sleeve-white-mini-dress https://www.alelly.net/collections/dresses/products/spaghetti-straps-silk-like-ruched-mini-dress https://www.alelly.net/collections/dresses/products/ruffled-off-shoulder-floral-dress https://www.alelly.net/collections/dresses/products/halloween-pumpkin-letter-print-striped-raglan-long-sleeve-mini-dress https://www.alelly.net/collections/dresses/products/crew-neck-twist-hollow-out-t-shirt-mini-dress-with-ruched-detail https://www.alelly.net/collections/dresses/products/asymmetric-cold-shoulder-denim-dress https://www.alelly.net/collections/dresses/products/velvet-puff-sleeve-mini-dress https://www.alelly.net/collections/dresses/products/leopard-print-spaghetti-strap-bodycon-mini-dress https://www.alelly.net/collections/dresses/products/wrap-v-neck-long-sleeve-ruched-velvet-mini-dress https://www.alelly.net/collections/dresses/products/pocket-lace-up-drawstring-hooded-mini-dress https://www.alelly.net/collections/dresses/products/plaid-striped-splicing-raglan-sleeve-mini-dress https://www.alelly.net/collections/dresses/products/long-sleeves-sequin-mini-dress https://www.alelly.net/collections/dresses/products/khaki-vintage-print-v-neck-lace-stitching-loose-dress
[Kernel-packages] [Bug 1951295] Re: Focal update: v5.4.156 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951295 Title: Focal update: v5.4.156 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.156 upstream stable release from git://git.kernel.org/ parisc: math-emu: Fix fall-through warnings net: switchdev: do not propagate bridge updates across bridges tee: optee: Fix missing devices unregister during optee_remove ARM: dts: at91: sama5d2_som1_ek: disable ISC node by default xtensa: xtfpga: use CONFIG_USE_OF instead of CONFIG_OF xtensa: xtfpga: Try software restart before simulating CPU reset NFSD: Keep existing listeners on portlist error dma-debug: fix sg checks in debug_dma_map_sg() ASoC: wm8960: Fix clock configuration on slave mode netfilter: ipvs: make global sysctl readonly in non-init netns lan78xx: select CRC32 net: dsa: lantiq_gswip: fix register definition NIOS2: irqflags: rename a redefined register name net: hns3: reset DWRR of unused tc to zero net: hns3: add limit ets dwrr bandwidth cannot be 0 net: hns3: disable sriov before unload hclge layer net: stmmac: Fix E2E delay mechanism net: enetc: fix ethtool counter name for PM0_TERR can: rcar_can: fix suspend/resume can: peak_usb: pcan_usb_fd_decode_status(): fix back to ERROR_ACTIVE state notification can: peak_pci: peak_pci_remove(): fix UAF can: j1939: j1939_tp_rxtimer(): fix errant alert in j1939_tp_rxtimer can: j1939: j1939_netdev_start(): fix UAF for rx_kref of j1939_priv can: j1939: j1939_xtp_rx_dat_one(): cancel session if receive TP.DT with error length can: j1939: j1939_xtp_rx_rts_session_new(): abort TP less than 9 bytes ceph: fix handling of "meta" errors ocfs2: fix data corruption after conversion from inline format ocfs2: mount fails with buffer overflow in strlen elfcore: correct reference to CONFIG_UML vfs: check fd has read access in kernel_read_file_from_fd() ALSA: usb-audio: Provide quirk for Sennheiser GSP670 Headset ALSA: hda/realtek: Add quirk for Clevo PC50HS ASoC: DAPM: Fix missing kctl change notifications audit: fix possible null-pointer dereference in audit_filter_rules powerpc64/idle: Fix SP offsets when saving GPRs KVM: PPC: Book3S HV: Fix stack handling in idle_kvm_start_guest() KVM: PPC: Book3S HV: Make idle_kvm_start_guest() return 0 if it went to guest powerpc/idle: Don't corrupt back chain when going idle mm, slub: fix mismatch between reconstructed freelist depth and cnt mm, slub: fix potential memoryleak in kmem_cache_open() nfc: nci: fix the UAF of rf_conn_info object isdn: cpai: check ctr->cnr to avoid array index out of bound netfilter: Kconfig: use 'default y' instead of 'm' for bool config option selftests: netfilter: remove stray bash debug line gcc-plugins/structleak: add makefile var for disabling structleak btrfs: deal with errors when checking if a dir entry exists during log replay net: stmmac: add support for dwmac 3.40a ARM: dts: spear3xx: Fix gmac node isdn: mISDN: Fix sleeping function called from invalid context platform/x86: intel_scu_ipc: Update timeout value in comment ALSA: hda: avoid write to STATESTS if controller is in reset Input: snvs_pwrkey - add clk handling scsi: core: Fix shost->cmd_per_lun calculation in scsi_add_host_with_dma() tracing: Have all levels of checks prevent recursion ARM: 9122/1: select HAVE_FUTEX_CMPXCHG pinctrl: stm32: use valid pin identifier in stm32_pinctrl_resume() Linux 5.4.156 UBUNTU: upstream stable to v5.4.156 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951295/+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 1951288] Re: Focal update: v5.4.154 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951288 Title: Focal update: v5.4.154 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.154 upstream stable release from git://git.kernel.org/ net: phy: bcm7xxx: Fixed indirect MMD operations ext4: correct the error path of ext4_write_inline_data_end() HID: apple: Fix logical maximum and usage maximum of Magic Keyboard JIS netfilter: ip6_tables: zero-initialize fragment offset HID: wacom: Add new Intuos BT (CTL-4100WL/CTL-6100WL) device IDs netfilter: nf_nat_masquerade: make async masq_inet6_event handling generic netfilter: nf_nat_masquerade: defer conntrack walk to work queue mac80211: Drop frames from invalid MAC address in ad-hoc mode m68k: Handle arrivals of multiple signals correctly net: prevent user from passing illegal stab size mac80211: check return value of rhashtable_init net: sun: SUNVNET_COMMON should depend on INET drm/amdgpu: fix gart.bo pin_count leak scsi: ses: Fix unsigned comparison with less than zero scsi: virtio_scsi: Fix spelling mistake "Unsupport" -> "Unsupported" sched: Always inline is_percpu_thread() Linux 5.4.154 UBUNTU: upstream stable to v5.4.154 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951288/+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 1951291] Re: Focal update: v5.4.155 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951291 Title: Focal update: v5.4.155 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.155 upstream stable release from git://git.kernel.org/ ovl: simplify file splice ALSA: usb-audio: Add quirk for VF0770 ALSA: seq: Fix a potential UAF by wrong private_free call order ALSA: hda/realtek: Complete partial device name to avoid ambiguity ALSA: hda/realtek: Add quirk for Clevo X170KM-G ALSA: hda/realtek - ALC236 headset MIC recording issue ALSA: hda/realtek: Fix the mic type detection issue for ASUS G551JW nds32/ftrace: Fix Error: invalid operands (*UND* and *UND* sections) for `^' s390: fix strrchr() implementation csky: don't let sigreturn play with priveleged bits of status register csky: Fixup regs.sr broken in ptrace btrfs: unlock newly allocated extent buffer after error btrfs: deal with errors when replaying dir entry during log replay btrfs: deal with errors when adding inode reference during log replay btrfs: check for error when looking up inode during dir entry replay watchdog: orion: use 0 for unset heartbeat x86/resctrl: Free the ctrlval arrays when domain_setup_mon_state() fails mei: me: add Ice Lake-N device id. xhci: guard accesses to ep_state in xhci_endpoint_reset() xhci: Fix command ring pointer corruption while aborting a command xhci: Enable trust tx length quirk for Fresco FL11 USB controller cb710: avoid NULL pointer subtraction efi/cper: use stack buffer for error record decoding efi: Change down_interruptible() in virt_efi_reset_system() to down_trylock() usb: musb: dsps: Fix the probe error path Input: xpad - add support for another USB ID of Nacon GC-100 USB: serial: qcserial: add EM9191 QDL support USB: serial: option: add Quectel EC200S-CN module support USB: serial: option: add Telit LE910Cx composition 0x1204 USB: serial: option: add prod. id for Quectel EG91 virtio: write back F_VERSION_1 before validate EDAC/armada-xp: Fix output of uncorrectable error counter nvmem: Fix shift-out-of-bound (UBSAN) with byte size cells x86/Kconfig: Do not enable AMD_MEM_ENCRYPT_ACTIVE_BY_DEFAULT automatically powerpc/xive: Discard disabled interrupts in get_irqchip_state() iio: adc: aspeed: set driver data when adc probe. iio: adc128s052: Fix the error handling path of 'adc128_probe()' iio: mtk-auxadc: fix case IIO_CHAN_INFO_PROCESSED iio: light: opt3001: Fixed timeout error when 0 lux iio: ssp_sensors: add more range checking in ssp_parse_dataframe() iio: ssp_sensors: fix error code in ssp_print_mcu_debug() iio: dac: ti-dac5571: fix an error code in probe() sctp: account stream padding length for reconf chunk gpio: pca953x: Improve bias setting net: arc: select CRC32 net: korina: select CRC32 net/mlx5e: Mutually exclude RX-FCS and RX-port-timestamp net: stmmac: fix get_hw_feature() on old hardware net: encx24j600: check error in devm_regmap_init_encx24j600 ethernet: s2io: fix setting mac address during resume nfc: fix error handling of nfc_proto_register() NFC: digital: fix possible memory leak in digital_tg_listen_mdaa() NFC: digital: fix possible memory leak in digital_in_send_sdd_req() pata_legacy: fix a couple uninitialized variable bugs ata: ahci_platform: fix null-ptr-deref in ahci_platform_enable_regulators() mlxsw: thermal: Fix out-of-bounds memory accesses platform/mellanox: mlxreg-io: Fix argument base in kstrtou32() call drm/panel: olimex-lcd-olinuxino: select CRC32 drm/msm: Fix null pointer dereference on pointer edp drm/msm/dsi: Fix an error code in msm_dsi_modeset_init() drm/msm/dsi: fix off by one in dsi_bus_clk_enable error handling acpi/arm64: fix next_platform_timer() section mismatch error mqprio: Correct stats in mqprio_dump_class_stats(). qed: Fix missing error code in qed_slowpath_start() r8152: select CRC32 and CRYPTO/CRYPTO_HASH/CRYPTO_SHA256 ionic: don't remove netdev->dev_addr when syncing uc list Linux 5.4.155 UBUNTU: upstream stable to v5.4.155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951291/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1951643] Re: Hirsute update: upstream stable patchset 2021-11-19
** Changed in: linux (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951643 Title: Hirsute update: upstream stable patchset 2021-11-19 Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-19 Ported from the following upstream stable releases: v5.10.73, v5.14.12 from git://git.kernel.org/ Partially revert "usb: Kconfig: using select for USB_COMMON dependency" usb: chipidea: ci_hdrc_imx: Also search for 'phys' phandle USB: cdc-acm: fix racy tty buffer accesses USB: cdc-acm: fix break reporting usb: typec: tcpm: handle SRC_STARTUP state if cc changes drm/nouveau/kms/tu102-: delay enabling cursor until after assign_windows xen/privcmd: fix error handling in mmap-resource processing mmc: meson-gx: do not use memcpy_to/fromio for dram-access-quirk mmc: sdhci-of-at91: wait for calibration done before proceed mmc: sdhci-of-at91: replace while loop with read_poll_timeout ovl: fix missing negative dentry check in ovl_rename() ovl: fix IOCB_DIRECT if underlying fs doesn't support direct IO nfsd: fix error handling of register_pernet_subsys() in init_nfsd() nfsd4: Handle the NFSv4 READDIR 'dircount' hint being zero SUNRPC: fix sign error causing rpcsec_gss drops xen/balloon: fix cancelled balloon action ARM: dts: omap3430-sdp: Fix NAND device node ARM: dts: imx6dl-yapp4: Fix lp5562 LED driver probe ARM: dts: qcom: apq8064: use compatible which contains chipid riscv: Flush current cpu icache before other cpus bus: ti-sysc: Add break in switch statement in sysc_init_soc() soc: qcom: socinfo: Fixed argument passed to platform_set_data() ARM: dts: qcom: apq8064: Use 27MHz PXO clock as DSI PLL reference ARM: at91: pm: do not panic if ram controllers are not enabled soc: qcom: mdt_loader: Drop PT_LOAD check on hash segment ARM: dts: imx: Add missing pinctrl-names for panel on M53Menlo ARM: dts: imx: Fix USB host power regulator polarity on M53Menlo ARM: dts: imx6qdl-pico: Fix Ethernet support PCI: hv: Fix sleep while in non-sleep context when removing child devices from the bus ath5k: fix building with LEDS=m arm64: dts: qcom: pm8150: use qcom,pm8998-pon binding xtensa: use CONFIG_USE_OF instead of CONFIG_OF xtensa: call irqchip_init only when CONFIG_USE_OF is selected iwlwifi: pcie: add configuration of a Wi-Fi adapter on Dell XPS 15 bpf, arm: Fix register clobbering in div/mod implementation soc: ti: omap-prm: Fix external abort for am335x pruss bpf: Fix integer overflow in prealloc_elems_and_freelist() net/mlx5e: IPSEC RX, enable checksum complete net/mlx5: E-Switch, Fix double allocation of acl flow counter phy: mdio: fix memory leak net_sched: fix NULL deref in fifo_set_limit() powerpc/fsl/dts: Fix phy-connection-type for fm1mac3 ptp_pch: Load module automatically if ID matches dt-bindings: drm/bridge: ti-sn65dsi86: Fix reg value ARM: imx6: disable the GIC CPU interface before calling stby-poweroff sequence net: bridge: use nla_total_size_64bit() in br_get_linkxstats_size() net: bridge: fix under estimation in br_get_linkxstats_size() net/sched: sch_taprio: properly cancel timer from taprio_destroy() net: sfp: Fix typo in state machine debug string netlink: annotate data races around nlk->bound bus: ti-sysc: Use CLKDM_NOAUTO for dra7 dcan1 for errata i893 drm/sun4i: dw-hdmi: Fix HDMI PHY clock setup video: fbdev: gbefb: Only instantiate device when built for IP32 drm/nouveau: avoid a use-after-free when BO init fails drm/nouveau/kms/nv50-: fix file release memory leak drm/nouveau/debugfs: fix file release memory leak gve: Correct available tx qpl check gve: Avoid freeing NULL pointer rtnetlink: fix if_nlmsg_stats_size() under estimation gve: fix gve_get_stats() gve: report 64bit tx_bytes counter from gve_handle_report_stats() i40e: fix endless loop under rtnl i40e: Fix freeing of uninitialized misc IRQ vector net: prefer socket bound to interface when not in VRF powerpc/iommu: Report the correct most efficient DMA mask for PCI devices i2c: acpi: fix resource leak in reconfiguration device addition i2c: mediatek: Add OFFSET_EXT_CONF setting back riscv/vdso: make arch_setup_additional_pages wait
[Kernel-packages] [Bug 1951460] Re: Impish update: upstream stable patchset 2021-11-18
** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951460 Title: Impish update: upstream stable patchset 2021-11-18 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-18 Ported from the following upstream stable releases: v5.10.73, v5.14.12 from git://git.kernel.org/ Partially revert "usb: Kconfig: using select for USB_COMMON dependency" usb: chipidea: ci_hdrc_imx: Also search for 'phys' phandle USB: cdc-acm: fix racy tty buffer accesses USB: cdc-acm: fix break reporting usb: typec: tcpm: handle SRC_STARTUP state if cc changes drm/nouveau/kms/tu102-: delay enabling cursor until after assign_windows xen/privcmd: fix error handling in mmap-resource processing mmc: meson-gx: do not use memcpy_to/fromio for dram-access-quirk mmc: sdhci-of-at91: wait for calibration done before proceed mmc: sdhci-of-at91: replace while loop with read_poll_timeout ovl: fix missing negative dentry check in ovl_rename() ovl: fix IOCB_DIRECT if underlying fs doesn't support direct IO nfsd: fix error handling of register_pernet_subsys() in init_nfsd() nfsd4: Handle the NFSv4 READDIR 'dircount' hint being zero SUNRPC: fix sign error causing rpcsec_gss drops xen/balloon: fix cancelled balloon action ARM: dts: omap3430-sdp: Fix NAND device node ARM: dts: imx6dl-yapp4: Fix lp5562 LED driver probe ARM: dts: qcom: apq8064: use compatible which contains chipid riscv: Flush current cpu icache before other cpus bus: ti-sysc: Add break in switch statement in sysc_init_soc() soc: qcom: socinfo: Fixed argument passed to platform_set_data() ARM: dts: qcom: apq8064: Use 27MHz PXO clock as DSI PLL reference ARM: at91: pm: do not panic if ram controllers are not enabled soc: qcom: mdt_loader: Drop PT_LOAD check on hash segment ARM: dts: imx: Add missing pinctrl-names for panel on M53Menlo ARM: dts: imx: Fix USB host power regulator polarity on M53Menlo ARM: dts: imx6qdl-pico: Fix Ethernet support PCI: hv: Fix sleep while in non-sleep context when removing child devices from the bus ath5k: fix building with LEDS=m arm64: dts: qcom: pm8150: use qcom,pm8998-pon binding xtensa: use CONFIG_USE_OF instead of CONFIG_OF xtensa: call irqchip_init only when CONFIG_USE_OF is selected iwlwifi: pcie: add configuration of a Wi-Fi adapter on Dell XPS 15 bpf, arm: Fix register clobbering in div/mod implementation soc: ti: omap-prm: Fix external abort for am335x pruss bpf: Fix integer overflow in prealloc_elems_and_freelist() net/mlx5e: IPSEC RX, enable checksum complete net/mlx5: E-Switch, Fix double allocation of acl flow counter phy: mdio: fix memory leak net_sched: fix NULL deref in fifo_set_limit() powerpc/fsl/dts: Fix phy-connection-type for fm1mac3 ptp_pch: Load module automatically if ID matches dt-bindings: drm/bridge: ti-sn65dsi86: Fix reg value ARM: imx6: disable the GIC CPU interface before calling stby-poweroff sequence net: bridge: use nla_total_size_64bit() in br_get_linkxstats_size() net: bridge: fix under estimation in br_get_linkxstats_size() net/sched: sch_taprio: properly cancel timer from taprio_destroy() net: sfp: Fix typo in state machine debug string netlink: annotate data races around nlk->bound bus: ti-sysc: Use CLKDM_NOAUTO for dra7 dcan1 for errata i893 drm/sun4i: dw-hdmi: Fix HDMI PHY clock setup video: fbdev: gbefb: Only instantiate device when built for IP32 drm/nouveau: avoid a use-after-free when BO init fails drm/nouveau/kms/nv50-: fix file release memory leak drm/nouveau/debugfs: fix file release memory leak gve: Correct available tx qpl check gve: Avoid freeing NULL pointer rtnetlink: fix if_nlmsg_stats_size() under estimation gve: fix gve_get_stats() gve: report 64bit tx_bytes counter from gve_handle_report_stats() i40e: fix endless loop under rtnl i40e: Fix freeing of uninitialized misc IRQ vector net: prefer socket bound to interface when not in VRF powerpc/iommu: Report the correct most efficient DMA mask for PCI devices i2c: acpi: fix resource leak in reconfiguration device addition i2c: mediatek: Add OFFSET_EXT_CONF setting back riscv/vdso: make arch_setup_additional_pages wait for
[Kernel-packages] [Bug 1951784] 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 1951784 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-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1951784 Title: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0 Status in linux package in Ubuntu: Incomplete Status in linux-signed-hwe-5.11 package in Ubuntu: New Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: [Summary] I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard test always fails. I found that after CPU offline test, I can't read/write SD card. After checking dmesg, I got those error msgs. [ 232.577510] __common_interrupt: 7.34 No irq handler for vector [ 234.354327] mmc0: error -110 doing runtime resume I found the same issue on Dell Precision 3551(202002-27718) and Dell Precision 5530(201807-26342) in 5.13.0-21 and 5.11.0-36 Before I didn't think it's a bug since I re-run mediacard test then it's pass. But this cycle there are more systems failed to the test, I just started digging into that. [Step to reproduce] 1. install ubuntu-20.04.2/ubuntu-21.10/ubuntu-21.04 2. sudo apt update; sudo apt dist-upgrade -y 3. run cpu offline test via checkbox-cli or execute following command for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; done; cd $mount_point_of_sd_card sudo dd if=/dev/urandom of=test bs=1M count=10 [Expected result] Can read/write SD card. [Actual result] Can't read/write SD card. [Failure rate] 5/5 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 22 01:28:59 2021 InstallationDate: Installed on 2020-08-03 (475 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945967] Re: rtw89 kernel module for Realtek 8852 wifi is missing
I'm on the 5.13.0-22, maybe the 5.15 has a few different commits ? -- 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/1945967 Title: rtw89 kernel module for Realtek 8852 wifi is missing Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Confirmed Bug description: == SRU Justification == [Impact] Realtek 8852AE, which is used by many new laptops, doesn't have a driver. [Fix] Add rtw89 driver to support Realtek 8852AE. [Test] After applying the patch, 8852AE can scan, connect and do TX/RX. [Where problems could occur] This is a brand new driver, unless the driver hits some subtle PCI or IOMMU bugs, there isn't much chance to introduce any regression. == Original Bug Report == Hi, Resulting: no wifi adapter detected. Currently WIP: https://patchwork.kernel.org/project/linux-wireless/list/?series=534633=* Workaround: use https://github.com/lwfinger/rtw89 that allows to build a dkms deb package. Ubuntu Impish kernel 5.13 (or 5.15 from unstable ppa) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fthx 4574 F pulseaudio /dev/snd/controlC2: fthx 4574 F pulseaudio /dev/snd/controlC0: fthx 4574 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-09-15 (20 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210910) MachineType: LENOVO 21AVFR Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-4-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-4.4-generic 5.15.0-rc4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-5.15.0-4-generic N/A linux-backports-modules-5.15.0-4-generic N/A linux-firmware1.201 Tags: wayland-session impish Uname: Linux 5.15.0-4-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: 06/21/2021 dmi.bios.release: 1.9 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET39W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 21AVFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrR1MET39W(1.09):bd06/21/2021:br1.9:efr1.9:svnLENOVO:pn21AVFR:pvrThinkPadP14sGen2a:rvnLENOVO:rn21AVFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21AVFR dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951784] 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 1951784 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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1951784 Title: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0 Status in linux package in Ubuntu: New Status in linux-signed-hwe-5.11 package in Ubuntu: New Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: [Summary] I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard test always fails. I found that after CPU offline test, I can't read/write SD card. After checking dmesg, I got those error msgs. [ 232.577510] __common_interrupt: 7.34 No irq handler for vector [ 234.354327] mmc0: error -110 doing runtime resume I found the same issue on Dell Precision 3551(202002-27718) and Dell Precision 5530(201807-26342) in 5.13.0-21 and 5.11.0-36 Before I didn't think it's a bug since I re-run mediacard test then it's pass. But this cycle there are more systems failed to the test, I just started digging into that. [Step to reproduce] 1. install ubuntu-20.04.2/ubuntu-21.10/ubuntu-21.04 2. sudo apt update; sudo apt dist-upgrade -y 3. run cpu offline test via checkbox-cli or execute following command for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; done; cd $mount_point_of_sd_card sudo dd if=/dev/urandom of=test bs=1M count=10 [Expected result] Can read/write SD card. [Actual result] Can't read/write SD card. [Failure rate] 5/5 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 22 01:28:59 2021 InstallationDate: Installed on 2020-08-03 (475 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951784] Re: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1951784 Title: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0 Status in linux package in Ubuntu: New Status in linux-signed-hwe-5.11 package in Ubuntu: New Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: [Summary] I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard test always fails. I found that after CPU offline test, I can't read/write SD card. After checking dmesg, I got those error msgs. [ 232.577510] __common_interrupt: 7.34 No irq handler for vector [ 234.354327] mmc0: error -110 doing runtime resume I found the same issue on Dell Precision 3551(202002-27718) and Dell Precision 5530(201807-26342) in 5.13.0-21 and 5.11.0-36 Before I didn't think it's a bug since I re-run mediacard test then it's pass. But this cycle there are more systems failed to the test, I just started digging into that. [Step to reproduce] 1. install ubuntu-20.04.2/ubuntu-21.10/ubuntu-21.04 2. sudo apt update; sudo apt dist-upgrade -y 3. run cpu offline test via checkbox-cli or execute following command for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; done; cd $mount_point_of_sd_card sudo dd if=/dev/urandom of=test bs=1M count=10 [Expected result] Can read/write SD card. [Actual result] Can't read/write SD card. [Failure rate] 5/5 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 22 01:28:59 2021 InstallationDate: Installed on 2020-08-03 (475 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951784] Re: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1951784 Title: Can't read/write SD card after running CPU offline test in 5.11.0 and 5.13.0 Status in linux package in Ubuntu: New Status in linux-signed-hwe-5.11 package in Ubuntu: New Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: [Summary] I'm reviewing SRU testing on Dell XPS 13 7390(201906-27131) and mediacard test always fails. I found that after CPU offline test, I can't read/write SD card. After checking dmesg, I got those error msgs. [ 232.577510] __common_interrupt: 7.34 No irq handler for vector [ 234.354327] mmc0: error -110 doing runtime resume I found the same issue on Dell Precision 3551(202002-27718) and Dell Precision 5530(201807-26342) in 5.13.0-21 and 5.11.0-36 Before I didn't think it's a bug since I re-run mediacard test then it's pass. But this cycle there are more systems failed to the test, I just started digging into that. [Step to reproduce] 1. install ubuntu-20.04.2/ubuntu-21.10/ubuntu-21.04 2. sudo apt update; sudo apt dist-upgrade -y 3. run cpu offline test via checkbox-cli or execute following command for ((i=1;i<=$(nproc --all) -1;i++));do sudo chcpu -d $i;sudo chcpu -e $i; done; cd $mount_point_of_sd_card sudo dd if=/dev/urandom of=test bs=1M count=10 [Expected result] Can read/write SD card. [Actual result] Can't read/write SD card. [Failure rate] 5/5 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-41-generic 5.11.0-41.45~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 22 01:28:59 2021 InstallationDate: Installed on 2020-08-03 (475 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1798363] Re: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535)
The same error Xubuntu Linux 20.04.3 Linux 5.11.0-40-generic on x86_64 AsusPRO BR1100CKA-GJ0382 (90NX03B1-M05180) i2c_hid i2c-ASUE1201:00: i2c_hid_get_input: incomplete report (16/65535) -- 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/1798363 Title: i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740053] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.740764] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.741478] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742205] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.742921] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.743624] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.744321] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745026] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.745714] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Oct 17 20:07:57 blurhy-FX503VD kernel: [ 1133.746420] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) Lots of these things ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: blurhy 2908 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 17 20:07:13 2018 InstallationDate: Installed on 2018-10-10 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. Bus 001 Device 003: ID 13d3:5666 IMC Networks Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. FX503VD ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX503VD.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX503VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: FX dmi.product.name: FX503VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798363/+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 1945367] Re: [nvidia] Graphics freeze
End off this bug !!! I have installed nvidia-driver-470 tested and updated by ubuntu, and the bug disappear !! I note that the version of the nvidia driver passed from 470.62 to 470.82, is it the reason why it works now ? i don't know. Thanks to the developer who have done the necessary :-) Have a good day. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1945367 Title: [nvidia] Graphics freeze Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: i open a second bug report because i have already freeze problem after the installation of nvidia drivers and reboot. Freeze become generally when i am using firefox and visioning a video with youtube. I specify that since the last bug report, i re install ubuntu with official .iso without other package non official. To create the report, i have to connect to the PC from another one with ssh. When i use ubuntu-bug, it is not possible to join nvidia-bug-report because the application dont give me the hand to finish the report. When i try to execute nvidia-bug-report, i have the same thing. To use the PC, i have to use nouveau drivers and intel Xe GPU with poor performances ... Thanks for help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.63.01 Tue Aug 3 20:44:16 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip Date: Tue Sep 28 21:13:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.63.01, 5.11.0-37-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-36-generic, x86_64: installed virtualbox, 6.1.26, 5.11.0-37-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2090] NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2090] InstallationDate: Installed on 2021-09-26 (1 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: Intel(R) Client Systems NUC11PHi7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-37-generic root=UUID=24658b6f-3e37-4376-bc2e-2207e961c9c8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2021 dmi.bios.release: 5.19 dmi.bios.vendor: Intel Corp. dmi.bios.version: PHTGL579.0063.2021.0707.1057 dmi.board.name: NUC11PHBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M26151-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 12.19 dmi.modalias: dmi:bvnIntelCorp.:bvrPHTGL579.0063.2021.0707.1057:bd07/07/2021:br5.19:efr12.19:svnIntel(R)ClientSystems:pnNUC11PHi7:pvrM26149-403:skuSWNUC11PHKi7C00:rvnIntelCorporation:rnNUC11PHBi7:rvrM26151-402:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: PH dmi.product.name: NUC11PHi7 dmi.product.sku: SWNUC11PHKi7C00 dmi.product.version: M26149-403 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1951822] [NEW] Jammy update: v5.15.3 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.3 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: 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/1951822 Title: Jammy update: v5.15.3 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.3 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951822/+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 1951820] [NEW] Jammy update: v5.15.4 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.4 upstream stable release from git://git.kernel.org/ Linux 5.15.4 Revert "ACPI: scan: Release PM resources blocked by unused objects" thermal: Fix NULL pointer dereferences in of_thermal_ functions perf/core: Avoid put_page() when GUP fails PCI: Add MSI masking quirk for Nvidia ION AHCI PCI/MSI: Deal with devices lying about their MSI mask capability parisc/entry: fix trace test in syscall exit path Bluetooth: btusb: Add support for TP-Link UB500 Adapter loop: Use blk_validate_block_size() to validate block size block: Add a helper to validate the block size fortify: Explicitly disable Clang support btrfs: zoned: allow preallocation for relocation inodes btrfs: check for relocation inodes on zoned btrfs in should_nocow btrfs: zoned: use regular writes for relocation btrfs: zoned: only allow one process to add pages to a relocation inode btrfs: zoned: add a dedicated data relocation block group btrfs: introduce btrfs_is_data_reloc_root KVM: Fix steal time asm constraints Revert "drm: fb_helper: fix CONFIG_FB dependency" Revert "drm: fb_helper: improve CONFIG_FB dependency" string: uninline memcpy_and_pad ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: 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/1951820 Title: Jammy update: v5.15.4 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.4 upstream stable release from git://git.kernel.org/ Linux 5.15.4 Revert "ACPI: scan: Release PM resources blocked by unused objects" thermal: Fix NULL pointer dereferences in of_thermal_ functions perf/core: Avoid put_page() when GUP fails PCI: Add MSI masking quirk for Nvidia ION AHCI PCI/MSI: Deal with devices lying about their MSI mask capability parisc/entry: fix trace test in syscall exit path Bluetooth: btusb: Add support for TP-Link UB500 Adapter loop: Use blk_validate_block_size() to validate block size block: Add a helper to validate the block size fortify: Explicitly disable Clang support btrfs: zoned: allow preallocation for relocation inodes btrfs: check for relocation inodes on zoned btrfs in should_nocow btrfs: zoned: use regular writes for relocation btrfs: zoned: only allow one process to add pages to a relocation inode btrfs: zoned: add a dedicated data relocation block group btrfs: introduce btrfs_is_data_reloc_root KVM: Fix steal time asm constraints Revert "drm: fb_helper: fix CONFIG_FB dependency" Revert "drm: fb_helper: improve CONFIG_FB dependency" string: uninline memcpy_and_pad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951820/+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 1951772] 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/1951772 Title: post upgrade, no video after suspend Status in linux package in Ubuntu: Confirmed Bug description: Suspend on desktop worked fine before upgrade to impish. Post upgrade, coming up after suspend leaves monitors with no signal from nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Sun Nov 21 20:47:15 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/tcsh SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-11-21 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951772] Re: post upgrade, no video after suspend
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951772 Title: post upgrade, no video after suspend Status in linux package in Ubuntu: Confirmed Bug description: Suspend on desktop worked fine before upgrade to impish. Post upgrade, coming up after suspend leaves monitors with no signal from nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Sun Nov 21 20:47:15 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/tcsh SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-11-21 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951772/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951772] [NEW] post upgrade, no video after suspend
You have been subscribed to a public bug: Suspend on desktop worked fine before upgrade to impish. Post upgrade, coming up after suspend leaves monitors with no signal from nvidia graphics card. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: XFCE Date: Sun Nov 21 20:47:15 2021 PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/tcsh SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-11-21 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade impish -- post upgrade, no video after suspend https://bugs.launchpad.net/bugs/1951772 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951815] [NEW] touchpad doesn't work at all for ideapad 5 15itl05
Public bug reported: when i check cat /proc/bus/input/devices there is no touchpad device. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-90-generic 5.4.0-90.101~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-90.101~18.04.1-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 22 11:20:32 2021 InstallationDate: Installed on 2021-09-27 (55 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1951815 Title: touchpad doesn't work at all for ideapad 5 15itl05 Status in linux-signed-hwe-5.4 package in Ubuntu: New Bug description: when i check cat /proc/bus/input/devices there is no touchpad device. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-90-generic 5.4.0-90.101~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-90.101~18.04.1-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 22 11:20:32 2021 InstallationDate: Installed on 2021-09-27 (55 days ago) InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 (20210915) SourcePackage: linux-signed-hwe-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.4/+bug/1951815/+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 1951157] Re: Impish update: upstream stable patchset 2021-11-16
** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951157 Title: Impish update: upstream stable patchset 2021-11-16 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-11-16 Ported from the following upstream stable releases: v5.10.72, v5.14.11 from git://git.kernel.org/ spi: rockchip: handle zero length transfers without timing out platform/x86: touchscreen_dmi: Add info for the Chuwi HiBook (CWI514) tablet platform/x86: touchscreen_dmi: Update info for the Chuwi Hi10 Plus (CWI527) tablet nfsd: back channel stuck in SEQ4_STATUS_CB_PATH_DOWN btrfs: replace BUG_ON() in btrfs_csum_one_bio() with proper error handling btrfs: fix mount failure due to past and transient device flush error net: mdio: introduce a shutdown method to mdio device drivers xen-netback: correct success/error reporting for the SKB-with-fraglist case sparc64: fix pci_iounmap() when CONFIG_PCI is not set ext2: fix sleeping in atomic bugs on error scsi: sd: Free scsi_disk device via put_device() usb: testusb: Fix for showing the connection speed usb: dwc2: check return value after calling platform_get_resource() habanalabs/gaudi: fix LBW RR configuration selftests: be sure to make khdr before other targets selftests:kvm: fix get_warnings_count() ignoring fscanf() return warn nvme-fc: update hardware queues before using them nvme-fc: avoid race between time out and tear down thermal/drivers/tsens: Fix wrong check for tzd in irq handlers scsi: ses: Retry failed Send/Receive Diagnostic commands irqchip/gic: Work around broken Renesas integration smb3: correct smb3 ACL security descriptor tools/vm/page-types: remove dependency on opt_file for idle page tracking selftests: KVM: Align SMCCC call with the spec in steal_time KVM: do not shrink halt_poll_ns below grow_start kvm: x86: Add AMD PMU MSRs to msrs_to_save_all[] KVM: x86: nSVM: restore int_vector in svm_clear_vintr perf/x86: Reset destroy callback on event init failure libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI for Samsung 860 and 870 SSD. afs: Add missing vnode validation checks platform/x86: gigabyte-wmi: add support for B550I Aorus Pro AX habanalabs/gaudi: use direct MSI in single mode habanalabs: fail collective wait when not supported selftests:kvm: fix get_trans_hugepagesz() ignoring fscanf() return warn selftests: kvm: move get_run_delay() into lib/test_util selftests: kvm: fix get_run_delay() ignoring fscanf() return warn Xen/gntdev: don't ignore kernel unmapping error swiotlb-xen: ensure to issue well-formed XENMEM_exchange requests x86/insn, tools/x86: Fix undefined behavior due to potential unaligned accesses io_uring: allow conditional reschedule for intensive iterators block: don't call rq_qos_ops->done_bio if the bio isn't tracked kasan: always respect CONFIG_KASAN_STACK UBUNTU: upstream stable to v5.10.72, v5.14.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951157/+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 1777238] Re: video lag - Every 5 seconds a freeze frame when playing video of any source
Help anyone -- 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/1777238 Title: video lag - Every 5 seconds a freeze frame when playing video of any source Status in linux package in Ubuntu: Confirmed Bug description: The problem exists for months and I didn't find a good answer on it. It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind the video the sounds continues, but the video stops), youtube, Hangouts and every software where video is played. I experienced that there are 2 things that can break it: - if I move the mouse out and in on the affected window (it doesn't work in full screen) - if I open the system monitor, the problem also disappears other people also face with this problem: https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194 https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04 Ubuntu 4.15.0-23.25-generic 4.15.18 it was upgraded from 16.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 16 14:34:26 2018 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2016-08-04 (680 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vandor 3436 F pulseaudio /dev/snd/controlC1: vandor 3436 F pulseaudio /dev/snd/controlC0: vandor 3436 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c InstallationDate: Installed on 2016-08-04 (681 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777238/+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 1777238] Re: video lag - Every 5 seconds a freeze frame when playing video of any source
The issue is still there. -- 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/1777238 Title: video lag - Every 5 seconds a freeze frame when playing video of any source Status in linux package in Ubuntu: Confirmed Bug description: The problem exists for months and I didn't find a good answer on it. It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind the video the sounds continues, but the video stops), youtube, Hangouts and every software where video is played. I experienced that there are 2 things that can break it: - if I move the mouse out and in on the affected window (it doesn't work in full screen) - if I open the system monitor, the problem also disappears other people also face with this problem: https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194 https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04 Ubuntu 4.15.0-23.25-generic 4.15.18 it was upgraded from 16.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 16 14:34:26 2018 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2016-08-04 (680 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vandor 3436 F pulseaudio /dev/snd/controlC1: vandor 3436 F pulseaudio /dev/snd/controlC0: vandor 3436 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c InstallationDate: Installed on 2016-08-04 (681 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777238/+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 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Unfortunately I don't have control on the generation of the ISOs, the best thing I can do is to set this bug to critical and ping people... ** Changed in: linux (Ubuntu Impish) Importance: High => Critical ** Changed in: linux (Ubuntu Jammy) Importance: High => Critical -- 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/1945590 Title: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Status in linux source package in Jammy: Confirmed Bug description: I installed the Ubuntu 21.10 beta and as soon as I boot I get the kernel panic that I am attaching. I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the 5.13 kernel I get the same problem, disabling the trackpad and trackpoint in the bios the problem disappears. Everything works with the 5.11 kernel. I remain available for further details and sorry for my lack of experience. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-16-generic 5.13.0-16.16 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pietro 1810 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 30 10:26:10 2021 InstallationDate: Installed on 2021-09-29 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20TA0033IX ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-16-generic N/A linux-backports-modules-5.13.0-16-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) dmi.bios.date: 09/02/2021 dmi.bios.release: 1.43 dmi.bios.vendor: LENOVO dmi.bios.version: R1EET43W(1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20TA0033IX dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E14 Gen 2 dmi.product.name: 20TA0033IX dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2 dmi.product.version: ThinkPad E14 Gen 2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+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 1929527] Re: Mark kprobe_args_user.tc in kselftest/ftrace as unsupported
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: In Progress => Won't Fix
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1929527
Title:
Mark kprobe_args_user.tc in kselftest/ftrace as unsupported
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Released
Status in linux-oem-5.6 source package in Focal:
Won't Fix
Bug description:
[Impact]
This kprobe_args_user.tc test will be marked as "unresolved" and once causing
failures in ftrace of our ubuntu_kernel_selftests (lp:1869227)
Our workaround is to blacklist this test in autotest-client-tests [1]
Note that with patch b730d668138cb3 ("ftrace/selftest: make unresolved
cases cause failure if --fail-unresolved set") available, an
unresolved case will not be treated as a failure unless we requested
so.
[1] https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py?id=a381d47a9004388730e825cd20566ef102a29399
[Fix]
* 1e11b7dbef17bb selftests/ftrace: Return unsupported for the unconfigured
features
With this patch it will be marked as unsupported, easier to understand
than unresolved.
This patch can be found in Groovy and newer releases, and this test
does not exist in Bionic and older releases.
[Test]
Tested on s390x / PowerPC, this will be marked as unsupported:
$ sudo ./ftracetest test.d/kprobe/kprobe_args_user.tc
=== Ftrace unit tests ===
[1] Kprobe event user-memory access [UNSUPPORTED]
# of passed: 0
# of failed: 0
# of unresolved: 0
# of untested: 0
# of unsupported: 1
# of xfailed: 0
# of undefined(test bug): 0
$ echo $?
0
[Where problems could occur]
Changes limited to testing tool, should not impact real kernel functionality.
With this patch and local workaround in autotest-client-tests removed we might
see failures in s390x / PowerPC in the future.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1929527/+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
