[Touch-packages] [Bug 1966203] Re: journal shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1."
We also encountered this issue in Ubuntu 22.04 on NVIDIA Jetson Platform. What is the official fix and when will the fix be landed on Ubuntu 22.04? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: journal shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." Status in snapd: Confirmed Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: Configuration: OS:jammy-live-server20220320-amd64.iso CPU:AMD EPYC 7702 64-Core Processor UEFI Version:D8E119A BMC Version:D8BT19I SSD:Intel 1.60TB NVMe SSD Boot mode:legacy Reproduce Steps: 1.Boot into BIOS and set boot mode to legacy 2.install ubuntu 22.04 on NVMe SSD 3.Check syslog log Current behaviors: syslog shows systemd-udevd errors in Ubuntu 22.04 Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2877]: nvme0n1p3: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p3' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2876]: nvme0n1p2: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p2' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2837]: nvme0n1p1: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p1' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2828]: sr0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/sr0' failed with exit code 1. Feb 9 10:16:19 len systemd-udevd[2850]: dm-0: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/dm-0' failed with exit code 1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2041779] Re: lscpu shows wrong L3 Cache size on NVIDIA Orin Nano
We tried lscpu 2.37.2, and it could also show correct information. So the fix change should be merged during 2.34 to 2.37. Please help on this issue to backport the fix change to 2.34 for Ubuntu focal. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2041779 Title: lscpu shows wrong L3 Cache size on NVIDIA Orin Nano Status in util-linux package in Ubuntu: New Bug description: For NVIDIA Orin Nano, L3 all cache size is 4M. But we got different result via lscpu comes from different version of util-linux: lscpu from util-linux 2.34 which is the default version in Ubuntu focal (20.04) and shows wrong information: # lscpu -C// lscpu bin from util-linux 2.34 NAME ONE-SIZE ALL-SIZE WAYS TYPELEVEL L1d 64K 384K4 Data1 L1i 64K 384K4 Instruction 1 L2 256K 1.5M8 Unified 2 L3 2M 2M 16 Unified 3 # lscpu L1d cache: 384 KiB L1i cache: 384 KiB L2 cache:1.5 MiB L3 cache:2 MiB lscpu from util-linux 2.39 shows correct information, and this version is only packaged for Ubuntu mantic (23.10): # lscpu -C// lscpu bin from util-linux 2.39 NAME ONE-SIZE ALL-SIZE WAYS TYPELEVEL SETS PHY-LINE COHERENCY-SIZE L1d 64K 384K4 Data1 256 64 L1i 64K 384K4 Instruction 1 256 64 L2 256K 1.5M8 Unified 2 512 64 L3 2M 4M 16 Unified 3 2048 64 # lscpu Caches (sum of all): L1d: 384 KiB (6 instances) L1i: 384 KiB (6 instances) L2:1.5 MiB (6 instances) L3:4 MiB (2 instances) Looks like there was a fix during version 2.34 to 2.39, but we need to use Ubuntu 20.04. Can you please backport the fix change to 2.34 then we can get correct information using default lscpu for Ubuntu 20.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2041779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2041779] [NEW] lscpu shows wrong L3 Cache size on NVIDIA Orin Nano
Public bug reported: For NVIDIA Orin Nano, L3 all cache size is 4M. But we got different result via lscpu comes from different version of util-linux: lscpu from util-linux 2.34 which is the default version in Ubuntu focal (20.04) and shows wrong information: # lscpu -C// lscpu bin from util-linux 2.34 NAME ONE-SIZE ALL-SIZE WAYS TYPELEVEL L1d 64K 384K4 Data1 L1i 64K 384K4 Instruction 1 L2 256K 1.5M8 Unified 2 L3 2M 2M 16 Unified 3 # lscpu L1d cache: 384 KiB L1i cache: 384 KiB L2 cache:1.5 MiB L3 cache:2 MiB lscpu from util-linux 2.39 shows correct information, and this version is only packaged for Ubuntu mantic (23.10): # lscpu -C// lscpu bin from util-linux 2.39 NAME ONE-SIZE ALL-SIZE WAYS TYPELEVEL SETS PHY-LINE COHERENCY-SIZE L1d 64K 384K4 Data1 256 64 L1i 64K 384K4 Instruction 1 256 64 L2 256K 1.5M8 Unified 2 512 64 L3 2M 4M 16 Unified 3 2048 64 # lscpu Caches (sum of all): L1d: 384 KiB (6 instances) L1i: 384 KiB (6 instances) L2:1.5 MiB (6 instances) L3:4 MiB (2 instances) Looks like there was a fix during version 2.34 to 2.39, but we need to use Ubuntu 20.04. Can you please backport the fix change to 2.34 then we can get correct information using default lscpu for Ubuntu 20.04? ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/2041779 Title: lscpu shows wrong L3 Cache size on NVIDIA Orin Nano Status in util-linux package in Ubuntu: New Bug description: For NVIDIA Orin Nano, L3 all cache size is 4M. But we got different result via lscpu comes from different version of util-linux: lscpu from util-linux 2.34 which is the default version in Ubuntu focal (20.04) and shows wrong information: # lscpu -C// lscpu bin from util-linux 2.34 NAME ONE-SIZE ALL-SIZE WAYS TYPELEVEL L1d 64K 384K4 Data1 L1i 64K 384K4 Instruction 1 L2 256K 1.5M8 Unified 2 L3 2M 2M 16 Unified 3 # lscpu L1d cache: 384 KiB L1i cache: 384 KiB L2 cache:1.5 MiB L3 cache:2 MiB lscpu from util-linux 2.39 shows correct information, and this version is only packaged for Ubuntu mantic (23.10): # lscpu -C// lscpu bin from util-linux 2.39 NAME ONE-SIZE ALL-SIZE WAYS TYPELEVEL SETS PHY-LINE COHERENCY-SIZE L1d 64K 384K4 Data1 256 64 L1i 64K 384K4 Instruction 1 256 64 L2 256K 1.5M8 Unified 2 512 64 L3 2M 4M 16 Unified 3 2048 64 # lscpu Caches (sum of all): L1d: 384 KiB (6 instances) L1i: 384 KiB (6 instances) L2:1.5 MiB (6 instances) L3:4 MiB (2 instances) Looks like there was a fix during version 2.34 to 2.39, but we need to use Ubuntu 20.04. Can you please backport the fix change to 2.34 then we can get correct information using default lscpu for Ubuntu 20.04? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2041779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access
This issue is still happened using focal-update. I checked below changelog for libegl-mesa0 package: - https://packages.ubuntu.com/focal/libegl-mesa0 - https://packages.ubuntu.com/focal-updates/libegl-mesa0 And found the change is only existed in focal, but not in focal-update: mesa (18.1.1-1ubuntu1) cosmic; urgency=medium * Merge from Debian. * glvnd-fix-a-segfault-in-eglgetprocaddess.diff: Backport a commit to fix a segfault. (LP: #1776499) -- Timo Aaltonen Wed, 13 Jun 2018 12:10:21 +0300 Timo, can we also have this fix landed in focal-update? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1776499 Title: Crash in libegl-mesa0 due to out of bound array access Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: Crash in libegl-mesa0 due to out of bound array access. Crash is fixed on Mesa master branch with change: https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d .This bug is to request to include this change in Mesa upgrades in bionic. Please let me know if this change needs to be back ported to other branch so that libegl-mesa0 upgrade in Bionic could pick this change. lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 18.0.0~rc5-1ubuntu1 Candidate: 18.0.0~rc5-1ubuntu1 Version table: *** 18.0.0~rc5-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
