[Bug 1977699] [NEW] zfs icp has deselected all optimized aes & gcm impls
Public bug reported: In an upgrade from Jammy kernel 5.15.0-27-generic to 5.15.0-35-generic on x86_64 (AMD threadripper pro 39x5wx series), a 40x performance regression in the first read of cached writes to an encrypted dataset revealed that zfs is no longer configured to choose any implementations from advanced instruction sets: $ grep . /sys/module/icp/parameters/*impl* /sys/module/icp/parameters/icp_aes_impl:cycle [fastest] generic x86_64 /sys/module/icp/parameters/icp_gcm_impl:cycle [fastest] generic With correct configuration, the output should read as follows: $ grep . /sys/module/icp/parameters/*impl* /sys/module/icp/parameters/icp_aes_impl:cycle [fastest] generic x86_64 aesni /sys/module/icp/parameters/icp_gcm_impl:cycle [fastest] avx generic pclmulqdq The immediate ill effects are the use of gcm_generic_mul instead of the dedicated instruction, consuming 50% CPU and slowing reads of data cached in ram to less than 20% of what they would be even reading directly from disk. openzfs changed its configure process to detect cpu features differently recently to adapt to the kernel api change. It seems that the upstream changes that unexport the needed symbols and the downstream changes in openzfs that stop using them were not cherrypicked in sync. https://github.com/openzfs/zfs/pull/13147 https://github.com/openzfs/zfs/pull/13236 ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977699 Title: zfs icp has deselected all optimized aes & gcm impls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1977699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870482] Re: apt-btrfs-snapshot blocks apt
i ran into this and figured out what it was. apt-btrfs-snapshot makes several assumptions when it operates, not all of which are checked: 1. / is mounted from a btrfs device subvolume named /@ 2. the btrfs filesystem on that device will mount the root filesystem, inside which @ resides. 1. is checked by "supported" by looking in fstab and ensuring that subvolid=@ is *explicitly* specified, 2. is not checked at all. if your volume root mounts @ as the default subvolume it's not gonna work! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870482 Title: apt-btrfs-snapshot blocks apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-btrfs-snapshot/+bug/1870482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802814] Re: GPU lockup with Vega 64 (amdgpu)
** Attachment added: "output from avivotool" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+attachment/5211605/+files/regdump-lockup.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802814 Title: GPU lockup with Vega 64 (amdgpu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802814] Re: GPU lockup with Vega 64 (amdgpu)
** Attachment added: "output from avivotool" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+attachment/5211606/+files/regdump-normal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802814 Title: GPU lockup with Vega 64 (amdgpu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802814] [NEW] GPU lockup with Vega 64 (amdgpu)
Public bug reported: This lockup is typically reproducible within 10-60 minutes running Dota 2, in either OpenGL or Vulkan mode. The application does not have exclusive control of the display, and is running as a borderless window in gdm's X desktop. When this lockup occurs, the mouse cursor may still move but cannot interact. The keyboard cannot interact, and mode lights (numlock) do not toggle. Sounds continue playing smoothly, but sound effects of limited duration will end naturally and nothing new will happen. The desktop no longer updates on the secondary monitor. I have dmesg and Xorg.0.log to attach. I'll also attach the output of 'sudo avivotool regs all', though I doubt its efficacy on this GPU and it shows nothing but ''. ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802814 Title: GPU lockup with Vega 64 (amdgpu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802814] Re: GPU lockup with Vega 64 (amdgpu)
** Attachment added: "dmesg-lockup.txt" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+attachment/5211603/+files/dmesg-lockup.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802814 Title: GPU lockup with Vega 64 (amdgpu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802814] Re: GPU lockup with Vega 64 (amdgpu)
** Attachment added: "Xorg.0.log-lockup.log" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+attachment/5211604/+files/Xorg.0.log-lockup.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802814 Title: GPU lockup with Vega 64 (amdgpu) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1802814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579181] Re: "pip3 list --outdated" raises TypeError
This is occurring for me with python3.6-dev==3.6.4-4 amd64 from bionic/main. Forcing a reinstall of the system's python3.6 pip package fixes it, but this is pretty lousy default behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579181 Title: "pip3 list --outdated" raises TypeError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1579181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579181] Re: "pip3 list --outdated" raises TypeError
I suppose I should clarify: the system pip package is python3-pip==9.0.1-2 amd64 from bionic/universe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579181 Title: "pip3 list --outdated" raises TypeError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1579181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
> sudo apt remove libegl1 This cascaded to what turned out to be the entirety of ubuntu-desktop for me. I would advise caution here, it can be a pain to get back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
