[Bug 2067527] Re: kernel BUG at crypto/algapi.c:431!
Quickly reproduces with: stress-ng --aggressive --verify --timeout 7200 --metrics-brief --tz --times --af-alg 0 --bsearch 0 --context 0 --cpu 0 --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 --matrix 0 --qsort 0 --str 0 --stream 0 --tsearch 0 --vecmath 0 --wcs 0 Using stress-ng 0.17.08-0~202405212140~ubuntu20.04.1 from ppa:checkbox-dev/stable -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067527 Title: kernel BUG at crypto/algapi.c:431! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067527] Re: kernel BUG at crypto/algapi.c:431!
We're also seeing a similar crash w/ 5.15.0: [24881.902027] [ cut here ] [24881.902068] WARNING: CPU: 7 PID: 2196586 at crypto/algapi.c:472 crypto_unregister_alg+0xfc/0 x108 [24881.902119] Modules linked in: aes_ce_blk(+) chacha_generic chacha_neon libchacha cfb xxhash _generic xcbc wp512 vmac sm3_generic poly1305_generic poly1305_neon nhpoly1305_neon nhpoly1305 libpoly1305 michael_mic md4 streebog_generic sha3_generic rmd160 crc32_generic cmac algif_rng t wofish_generic twofish_common serpent_generic fcrypt cast6_generic cast5_generic cast_common ca mellia_generic blowfish_generic blowfish_common aes_arm64 algif_skcipher algif_hash sm4_generic libsm4 ccm aes_ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg bridge stp llc nls _iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua binfmt_misc cavium_rng_vf thunder x_zip thunderx_edac cavium_rng ipmi_ssif ipmi_devintf uio_pdrv_genirq ipmi_msghandler uio sch_f q_codel ramoops reed_solomon pstore_blk pstore_zone efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 [24881.902474] multipath linear ast drm_vram_helper drm_ttm_helper ttm i2c_algo_bit drm_kms_he lper syscopyarea sysfillrect sysimgblt fb_sys_fops cec rc_core nicvf cavium_ptp drm nicpf thund er_bgx thunder_xcv mdio_thunder i2c_thunderx mdio_cavium thunderx_mmc xhci_pci ahci xhci_pci_re nesas gpio_keys crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce aes_neon_blk crypto_simd cry ptd aes_ce_cipher [24881.902624] CPU: 7 PID: 2196586 Comm: modprobe Not tainted 5.15.0-107-generic #117~20.04.1-U buntu [24881.902640] Hardware name: Cavium ThunderX CRB/To be filled by O.E.M., BIOS 5.11 12/12/2012 [24881.902646] pstate: 2045 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [24881.902654] pc : crypto_unregister_alg+0xfc/0x108 [24881.902662] lr : crypto_unregister_alg+0x8c/0x108 [24881.902667] sp : 800021f2b860 [24881.902671] x29: 800021f2b860 x28: ffef x27: 81955b00 [24881.902694] x26: 81955b80 x25: 81955b60 x24: 819551a0 [24881.902707] x23: 81955180 x22: 800021f2b898 x21: 8aafb9c8 [24881.902724] x20: 000832b82080 x19: 81956400 x18: [24881.902748] x17: 800fb49aa000 x16: 88038000 x15: 8a96b428 [24881.902769] x14: 8a96af50 x13: 0007 x12: 0008 [24881.902781] x11: 8a92db60 x10: 0bf0 x9 : 887744c4 [24881.902802] x8 : 000832b82cd0 x7 : 0425 x6 : 8aafba70 [24881.902829] x5 : x4 : x3 : [24881.902842] x2 : x1 : 0001 x0 : 004a [24881.902855] Call trace: [24881.902862] crypto_unregister_alg+0xfc/0x108 [24881.902870] crypto_unregister_skciphers+0x3c/0x58 [24881.902880] aes_exit+0x88/0xf0 [aes_ce_blk] [24881.902907] cpu_feature_match_AES_init+0x12c/0x1000 [aes_ce_blk] [24881.902920] do_one_initcall+0x50/0x258 [24881.902938] do_init_module+0x50/0x218 [24881.902957] load_module+0x10d4/0x15d8 [24881.902962] __do_sys_finit_module+0xbc/0x128 [24881.902968] __arm64_sys_finit_module+0x28/0x38 [24881.902973] invoke_syscall+0x74/0xf0 [24881.902989] el0_svc_common.constprop.0+0x58/0x1a8 [24881.902995] do_el0_svc+0x2c/0xa0 [24881.903011] el0_svc+0x40/0x138 [24881.903029] el0t_64_sync_handler+0xb0/0xb8 [24881.903036] el0t_64_sync+0x1a4/0x1a8 [24881.903050] ---[ end trace 48915fdb364cfcf7 ]--- [24882.589982] [ cut here ] [24882.590023] WARNING: CPU: 20 PID: 2197443 at crypto/algapi.c:472 crypto_unregister_alg+0xfc/0x108 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067527 Title: kernel BUG at crypto/algapi.c:431! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067527] [NEW] kernel BUG at crypto/algapi.c:431!
Public bug reported: Our ARM64 servers are tripping a BUG in the 5.4.0-182 kernel when running cert regression testing: bizzy login: [ 221.090860] kernel BUG at /build/linux-hwe-5.4-OMohr6/linux-hwe-5.4-5.4.0/crypto/algapi.c:431! [ 221.099468] Internal error: Oops - BUG: 0 [#1] SMP [ 221.104250] Modules linked in: aes_ce_blk(+) salsa20_generic pcbc ofb lrw chacha_neon chacha_generic cfb xxhash_generic xcbc wp512 vmac tgr192 sm3_generic rmd320 rmd256 rmd128 nhpoly1305_neon nhpoly1305 poly1305_generic michael_mic md4 streebog_generic sha3_generic rmd160 crc32_generic cmac algif_rng twofish_generic twofish_common tea serpent_generic seed khazad fcrypt cast6_generic cast5_generic cast_common camellia_generic blowfish_generic blowfish_common anubis aes_arm64 algif_skcipher algif_hash sm4_generic ccm aes_ce_ccm des_generic libdes authenc aegis128 algif_aead af_alg nls_iso8859_1 arm_spe_pmu ipmi_ssif joydev binfmt_misc input_leds cdc_ether usbnet ipmi_devintf ipmi_msghandler cppc_cpufreq xgene_hwmon acpi_tad sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath [ 221.104294] linear mlx5_ib hid_generic usbhid hid uas usb_storage ast i2c_algo_bit ib_uverbs drm_vram_helper ttm ib_core drm_kms_helper syscopyarea crct10dif_ce ghash_ce sha2_ce sysfillrect sha256_arm64 sysimgblt nvme fb_sys_fops sha1_ce mlx5_core drm nvme_core tls mlxfw aes_neon_blk crypto_simd cryptd aes_ce_cipher [ 221.219601] CPU: 66 PID: 26460 Comm: modprobe Not tainted 5.4.0-182-generic #202~18.04.1-Ubuntu [ 221.228286] Hardware name: WIWYNN Mt.Jade Server System B81.030Z1.0007/Mt.Jade Motherboard, BIOS 1.6.20210526 (SCP: 1.06.20210526) 2021/05/26 [ 221.240963] pstate: 2049 (nzCv daif +PAN -UAO) [ 221.245756] pc : crypto_unregister_alg+0xe8/0xf0 [ 221.250360] lr : crypto_unregister_alg+0x8c/0xf0 [ 221.254964] sp : 800043c2ba90 [ 221.258265] x29: 800043c2ba90 x28: 0100 [ 221.263564] x27: a8525f8fd8a8 x26: 0001 [ 221.268863] x25: 0001 x24: 369494c70e48 [ 221.274162] x23: a85251c08b10 x22: 800043c2bac8 [ 221.279460] x21: a85261875458 x20: a85260b17000 [ 221.284759] x19: a85251c08100 x18: [ 221.290057] x17: x16: a8525fd2fb40 [ 221.295355] x15: 401755505c001000 x14: [ 221.300653] x13: x12: 000b [ 221.305952] x11: 0010 x10: 0101010101010101 [ 221.311251] x9 : 0425 x8 : a85251c08110 [ 221.316550] x7 : 800043c2ba78 x6 : a85251c08110 [ 221.321848] x5 : 800043c2ba68 x4 : 800043c2ba78 [ 221.327146] x3 : dead0100 x2 : dead0122 [ 221.332445] x1 : e159eb2802a92900 x0 : 0003 [ 221.337745] Call trace: [ 221.340180] crypto_unregister_alg+0xe8/0xf0 [ 221.344439] crypto_unregister_skciphers+0x4c/0x60 [ 221.349222] aes_exit+0x5c/0x98 [aes_ce_blk] [ 221.353481] cpu_feature_match_AES_init+0xb4/0x1000 [aes_ce_blk] [ 221.359480] do_one_initcall+0x54/0x290 [ 221.363308] do_init_module+0x50/0x1fc [ 221.367049] load_module+0x1a48/0x2008 [ 221.370786] __do_sys_finit_module+0x100/0x118 [ 221.375217] __arm64_sys_finit_module+0x28/0x38 [ 221.379735] el0_svc_common.constprop.3+0x80/0x1f8 [ 221.384512] el0_svc_handler+0x34/0xb0 [ 221.388250] el0_svc+0x10/0x180 [ 221.391381] Code: aa1503e0 97ede3df 12800020 17f4 (d421) [ 221.397465] ---[ end trace 1ac9e656a151d682 ]--- [ 7418.231746] [ cut here ] ** Affects: 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/2067527 Title: kernel BUG at crypto/algapi.c:431! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2067527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061182] Re: mstflint-dkms no longer exists in mantic
I downloaded the deb from LP (that's why the verification starts w/ a `dpkg -i`). Apologies that I did not call that out, I honestly thought I had. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061182 Title: mstflint-dkms no longer exists in mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2061182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: Backport iproute2 6.8.0 to noble
I've now sync'd it to Oracular. ** Also affects: iproute2 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: iproute2 (Ubuntu Oracular) Importance: Undecided Status: Incomplete ** Changed in: iproute2 (Ubuntu Oracular) Status: Incomplete => Fix Committed ** Changed in: iproute2 (Ubuntu Oracular) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: iproute2 (Ubuntu Oracular) Milestone: ubuntu-24.04 => ubuntu-24.10-feature-freeze ** Changed in: iproute2 (Ubuntu Noble) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: Backport iproute2 6.8.0 to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061182] Re: mstflint-dkms no longer exists in mantic
# Verification ## Installs cleanly in mantic and builds against the mantic kernel: ubuntu@akis:~$ sudo dpkg -i *.deb Selecting previously unselected package mstflint-dkms. (Reading database ... 87552 files and directories currently installed.) Preparing to unpack mstflint-dkms_4.26.0+1-1ubuntu0.1_all.deb ... Unpacking mstflint-dkms (4.26.0+1-1ubuntu0.1) ... Preparing to unpack mstflint_4.21.0+1-1ubuntu0.1_amd64.deb ... Unpacking mstflint (4.21.0+1-1ubuntu0.1) over (4.21.0+1-1) ... dpkg: dependency problems prevent configuration of mstflint-dkms: mstflint-dkms depends on dkms (>= 2.1.0.0); however: Package dkms is not installed. mstflint-dkms depends on make; however: Package make is not installed. dpkg: error processing package mstflint-dkms (--install): dependency problems - leaving unconfigured Setting up mstflint (4.21.0+1-1ubuntu0.1) ... Processing triggers for man-db (2.11.2-3) ... Errors were encountered while processing: mstflint-dkms ubuntu@akis:~$ sudo apt -f install Reading package lists... Done Building dependency tree... Done Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: build-essential bzip2 cpp cpp-12 cpp-13 dkms dpkg-dev g++ g++-13 gcc gcc-12 gcc-12-base gcc-13 libalgorithm-diff-perl libalgorithm-diff-xs-perl libalgorithm-merge-perl libcc1-0 libdpkg-perl libfile-fcntllock-perl libgcc-12-dev libstdc++-13-dev lto-disabled-list make Suggested packages: bzip2-doc cpp-doc gcc-12-locales cpp-12-doc gcc-13-locales cpp-13-doc menu debian-keyring g++-multilib g++-13-multilib gcc-13-doc gcc-multilib autoconf automake libtool flex bison gdb gcc-doc gcc-12-multilib gcc-12-doc gcc-13-multilib bzr libstdc++-13-doc make-doc The following NEW packages will be installed: build-essential bzip2 cpp cpp-12 cpp-13 dkms dpkg-dev g++ g++-13 gcc gcc-12 gcc-12-base gcc-13 libalgorithm-diff-perl libalgorithm-diff-xs-perl libalgorithm-merge-perl libcc1-0 libdpkg-perl libfile-fcntllock-perl libgcc-12-dev libstdc++-13-dev lto-disabled-list make 0 upgraded, 23 newly installed, 0 to remove and 9 not upgraded. 1 not fully installed or removed. Need to get 83.6 MB of archives. After this operation, 277 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu mantic/main amd64 cpp-13 amd64 13.2.0-4ubuntu3 [10.7 MB] Get:2 http://archive.ubuntu.com/ubuntu mantic/main amd64 cpp amd64 4:13.2.0-1ubuntu1 [28.9 kB] Get:3 http://archive.ubuntu.com/ubuntu mantic/main amd64 libcc1-0 amd64 13.2.0-4ubuntu3 [48.0 kB] Get:4 http://archive.ubuntu.com/ubuntu mantic/main amd64 gcc-13 amd64 13.2.0-4ubuntu3 [21.5 MB] Get:5 http://archive.ubuntu.com/ubuntu mantic/main amd64 gcc amd64 4:13.2.0-1ubuntu1 [5168 B] Get:6 http://archive.ubuntu.com/ubuntu mantic/main amd64 gcc-12-base amd64 12.3.0-9ubuntu2 [43.6 kB] Get:7 http://archive.ubuntu.com/ubuntu mantic/main amd64 cpp-12 amd64 12.3.0-9ubuntu2 [10.8 MB] Get:8 http://archive.ubuntu.com/ubuntu mantic/main amd64 libgcc-12-dev amd64 12.3.0-9ubuntu2 [2574 kB] Get:9 http://archive.ubuntu.com/ubuntu mantic/main amd64 gcc-12 amd64 12.3.0-9ubuntu2 [21.6 MB] Get:10 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 libdpkg-perl all 1.22.0ubuntu1.1 [285 kB] Get:11 http://archive.ubuntu.com/ubuntu mantic/main amd64 bzip2 amd64 1.0.8-5build1 [34.8 kB] Get:12 http://archive.ubuntu.com/ubuntu mantic/main amd64 make amd64 4.3-4.1build1 [180 kB] Get:13 http://archive.ubuntu.com/ubuntu mantic/main amd64 lto-disabled-list all 43 [12.4 kB] Get:14 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 dpkg-dev all 1.22.0ubuntu1.1 [1137 kB] Get:15 http://archive.ubuntu.com/ubuntu mantic/main amd64 libstdc++-13-dev amd64 13.2.0-4ubuntu3 [2351 kB] Get:16 http://archive.ubuntu.com/ubuntu mantic/main amd64 g++-13 amd64 13.2.0-4ubuntu3 [12.1 MB] Get:17 http://archive.ubuntu.com/ubuntu mantic/main amd64 g++ amd64 4:13.2.0-1ubuntu1 [1122 B] Get:18 http://archive.ubuntu.com/ubuntu mantic/main amd64 build-essential amd64 12.10ubuntu1 [4928 B] Get:19 http://archive.ubuntu.com/ubuntu mantic/main amd64 dkms all 3.0.11-1ubuntu10 [51.3 kB] Get:20 http://archive.ubuntu.com/ubuntu mantic/main amd64 libalgorithm-diff-perl all 1.201-1 [41.8 kB] Get:21 http://archive.ubuntu.com/ubuntu mantic/main amd64 libalgorithm-diff-xs-perl amd64 0.04-8 [11.2 kB] Get:22 http://archive.ubuntu.com/ubuntu mantic/main amd64 libalgorithm-merge-perl all 0.08-5 [11.4 kB] Get:23 http://archive.ubuntu.com/ubuntu mantic/main amd64 libfile-fcntllock-perl amd64 0.22-4ubuntu1 [33.2 kB] Fetched 83.6 MB in 3s (28.8 MB/s) Selecting previously unselected package cpp-13. (Reading database ... 87562 files and directories currently installed.) Preparing to unpack .../00-cpp-13_13.2.0-4ubuntu3_amd64.deb ... Unpacking cpp-13 (13.2.0-4ubuntu3) ... Selecting previously unselected package cpp. Preparing to unpack
[Bug 2051571] Re: jammy: 4.21.0-7 dropped mstlink binary
# verification ubuntu@hinyari:~$ ls -l /usr/bin/mstflint /usr/bin/mstreg -rwxr-xr-x 1 root root 943848 Apr 12 20:33 /usr/bin/mstflint -rwxr-xr-x 1 root root 447160 Apr 12 20:33 /usr/bin/mstreg ubuntu@hinyari:~$ dpkg -l mstflint Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--===> ii mstflint 4.21.0+1-1ubuntu0.1~22.04.1 arm64Mellanox firmware burning a> ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051571 Title: jammy: 4.21.0-7 dropped mstlink binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2051571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061185] Re: mstflint-dkms module bug causes UBSAN errors in dmesg
# jammy verification ubuntu@hinyari:~$ uname -a Linux hinyari 6.5.0-28-generic-64k #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 5 16:55:05 UTC 2 aarch64 aarch64 aarch64 GNU/Linux ubuntu@hinyari:~$ sudo dmesg -c > /dev/null ubuntu@hinyari:~$ sudo mstflint -d 0006:01:00.0 q Image type:FS4 FW Version:26.33.1048 FW Release Date: 29.4.2022 Product Version: 26.33.1048 Rom Info: type=UEFI version=14.26.17 cpu=AMD64,AARCH64 type=PXE version=3.6.502 cpu=AMD64 Description: UIDGuidsNumber Base GUID: b83fd203001d37404 Base MAC: b83fd21d37404 Image VSD: N/A Device VSD:N/A PSID: MT_000531 Security Attributes: N/A ubuntu@hinyari:~$ sudo dmesg ubuntu@hinyari:~$ ** Tags removed: verification-needed verification-needed-jammy verification-needed-mantic ** Tags added: verification-done verification-done-jammy verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061185 Title: mstflint-dkms module bug causes UBSAN errors in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2061185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061185] Re: mstflint-dkms module bug causes UBSAN errors in dmesg
# mantic verification ubuntu@akis:~$ uname -a Linux akis 6.5.0-28-generic #29-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 28 23:46:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux ubuntu@akis:~$ sudo dmesg -c > /dev/null ubuntu@akis:~$ sudo mstflint -d 35:00.0 q Image type:FS4 FW Version:16.28.2040 FW Release Date: 6.10.2020 Product Version: 16.28.2040 Rom Info: type=UEFI version=14.21.17 cpu=AMD64 type=PXE version=3.6.102 cpu=AMD64 Description: UIDGuidsNumber Base GUID: 98039b03006383344 Base MAC: 98039b6383344 Image VSD: N/A Device VSD:N/A PSID: MT_10 Security Attributes: N/A ubuntu@akis:~$ sudo dmesg ubuntu@akis:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061185 Title: mstflint-dkms module bug causes UBSAN errors in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2061185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043098] Re: mstflint-dkms FTBS with linux 6.5 on jammy
# jammy verification ubuntu@hinyari:~$ sudo apt install mstflint-dkms Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: libnuma1 Use 'sudo apt autoremove' to remove it. The following packages will be upgraded: mstflint-dkms 1 upgraded, 0 newly installed, 0 to remove and 41 not upgraded. 1 not fully installed or removed. Need to get 19.0 kB of archives. After this operation, 4096 B of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/universe arm64 mstflint-dkms all 4.26.0+1-1ubuntu0.1~22.04.1 [19.0 kB] Fetched 19.0 kB in 0s (74.1 kB/s) (Reading database ... 134181 files and directories currently installed.) Preparing to unpack .../mstflint-dkms_4.26.0+1-1ubuntu0.1~22.04.1_all.deb ... Deleting module mstflint-4.21.0-7 completely from the DKMS tree. Unpacking mstflint-dkms (4.26.0+1-1ubuntu0.1~22.04.1) over (4.21.0-7) ... Setting up mstflint-dkms (4.26.0+1-1ubuntu0.1~22.04.1) ... Loading new mstflint-4.26.0+1-1ubuntu0.1~22.04.1 DKMS files... Building for 6.5.0-28-generic-64k 6.5.0-1015-nvidia-64k Building initial module for 6.5.0-28-generic-64k Can't load /var/lib/shim-signed/mok/.rnd into RNG 2000AC2B5DE4:error:1279:random number generator:RAND_load_file:Cannot open file: ../crypto/rand/randfile.c:106:Filename=/var/lib/shim-signed/mok/.rnd ...+..+.+..+.+++ +++*...+.+...+..+..+...+.+...+...+.+.+++ ++*+...+..+.+... +.+...+++.+.+.+. + .+..+...+...+...+..+...+.+..+... +*..+..+.+...+.+..+..+.+...+ *..+...+...++.+. +...+.+..+.+...+..+.+..+...+...+..+...+. ..+...++.+.+...+.+.++.+..+...+..+..+...+..+. ...+..+.++...++...+..+.+ +..+.+.+.+.++...+..+ .++.+.+...+..+.+...+.+..+...+... +..+...++...+..+..+.+.+...+..+...+..+...+... .++.++...+...+.+...+.+..++..+..+ .+...+.+..+...++...++...+...+...+...+...++.. +..+..+...+.+.++.+..+.+...+. ++..++...+..++.+...+...+..+.+.+..++.+... ..++..+.+...+..+.+..+..++...+..+...+..+. ...+...+..+..+.+.+.+.+.+..+.+..+..+. ...+...++...+..+.+.+.+.+ - Secure Boot not enabled on this system. Done. mstflint_access.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.5.0-28-generic-64k/updates/dkms/ depmod... Building initial module for 6.5.0-1015-nvidia-64k Secure Boot not enabled on this system. Done. mstflint_access.ko: Running module version sanity check. Good news! Module version 2.0.0 for mstflint_access.ko exactly matches what is already found in kernel 6.5.0-1015-nvidia-64k. DKMS will not replace this module. You may override by specifying --force. depmod... Scanning processes... Scanning candidates... Scanning processor microcode... Scanning linux images... Failed to check for processor microcode upgrades. Restarting services... systemctl restart cron.service multipathd.service packagekit.service polkit.service rsyslog.service serial-getty@ttyAMA0.service snapd.service ssh.service systemd-journald.service systemd-networkd.service systemd-resolved.service systemd-timesyncd.service systemd-udevd.service Service restarts being deferred: /etc/needrestart/restart.d/dbus.service systemctl restart getty@tty1.service systemctl restart networkd-dispatcher.service systemctl restart systemd-logind.service systemctl restart unattended-upgrades.service systemctl restart user@1000.service No containers need to be restarted. No user sessions are running outdated
[Bug 2061186] Re: mstflint_access kernel module licensing is inconsistent
# jammy verification ubuntu@hinyari:/usr/src/mstflint-4.26.0+1-1ubuntu0.1~22.04.1$ head -32 *.c *.h ==> mst_main.c <== /* * Copyright (c) 2021 NVIDIA CORPORATION & AFFILIATES. ALL RIGHTS RESERVED. * * This software is available to you under a choice of one of two * licenses. You may choose to be licensed under the terms of the GNU * General Public License (GPL) Version 2, available from the file * COPYING in the main directory of this source tree, or the * OpenIB.org BSD license below: * * Redistribution and use in source and binary forms, with or * without modification, are permitted provided that the following * conditions are met: * * - Redistributions of source code must retain the above *copyright notice, this list of conditions and the following *disclaimer. * * - Redistributions in binary form must reproduce the above *copyright notice, this list of conditions and the following *disclaimer in the documentation and/or other materials *provided with the distribution. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS * BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN * ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE * SOFTWARE. */ #include ==> mst_vpd.c <== /* * Copyright (c) 2021 NVIDIA CORPORATION & AFFILIATES. ALL RIGHTS RESERVED. * * This software is available to you under a choice of one of two * licenses. You may choose to be licensed under the terms of the GNU * General Public License (GPL) Version 2, available from the file * COPYING in the main directory of this source tree, or the * OpenIB.org BSD license below: * * Redistribution and use in source and binary forms, with or * without modification, are permitted provided that the following * conditions are met: * * - Redistributions of source code must retain the above *copyright notice, this list of conditions and the following *disclaimer. * * - Redistributions in binary form must reproduce the above *copyright notice, this list of conditions and the following *disclaimer in the documentation and/or other materials *provided with the distribution. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS * BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN * ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE * SOFTWARE. */ #include ==> mst.h <== /* * Copyright (c) 2023 NVIDIA CORPORATION & AFFILIATES. ALL RIGHTS RESERVED. * * This software is available to you under a choice of one of two * licenses. You may choose to be licensed under the terms of the GNU * General Public License (GPL) Version 2, available from the file * COPYING in the main directory of this source tree, or the * OpenIB.org BSD license below: * * Redistribution and use in source and binary forms, with or * without modification, are permitted provided that the following * conditions are met: * * - Redistributions of source code must retain the above *copyright notice, this list of conditions and the following *disclaimer. * * - Redistributions in binary form must reproduce the above *copyright notice, this list of conditions and the following *disclaimer in the documentation and/or other materials *provided with the distribution. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS * BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN * ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE * SOFTWARE. */ #ifndef _MST_H_ ==> mst_kernel.h <== /* * Copyright (c) 2023 NVIDIA CORPORATION & AFFILIATES. ALL RIGHTS RESERVED. * * This software is available to you under a choice of one of two * licenses. You may choose to be licensed under the terms of the GNU * General Public License (GPL) Version 2, available from the file * COPYING in the main directory of this source tree, or the * OpenIB.org BSD license below: * * Redistribution and use in source and binary forms, with or *
[Bug 2061186] Re: mstflint_access kernel module licensing is inconsistent
# mantic verification Licenses are now consistent. SPDX-License-Identifier is gone, and the boilerplate all says GPLv2 or OpenIB.org BSD: ubuntu@akis:/usr/src/mstflint-4.26.0+1-1ubuntu0.1$ head -32 *.c *.h ==> mst_main.c <== /* * Copyright (c) 2021 NVIDIA CORPORATION & AFFILIATES. ALL RIGHTS RESERVED. * * This software is available to you under a choice of one of two * licenses. You may choose to be licensed under the terms of the GNU * General Public License (GPL) Version 2, available from the file * COPYING in the main directory of this source tree, or the * OpenIB.org BSD license below: * * Redistribution and use in source and binary forms, with or * without modification, are permitted provided that the following * conditions are met: * * - Redistributions of source code must retain the above *copyright notice, this list of conditions and the following *disclaimer. * * - Redistributions in binary form must reproduce the above *copyright notice, this list of conditions and the following *disclaimer in the documentation and/or other materials *provided with the distribution. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS * BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN * ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE * SOFTWARE. */ #include ==> mst_vpd.c <== /* * Copyright (c) 2021 NVIDIA CORPORATION & AFFILIATES. ALL RIGHTS RESERVED. * * This software is available to you under a choice of one of two * licenses. You may choose to be licensed under the terms of the GNU * General Public License (GPL) Version 2, available from the file * COPYING in the main directory of this source tree, or the * OpenIB.org BSD license below: * * Redistribution and use in source and binary forms, with or * without modification, are permitted provided that the following * conditions are met: * * - Redistributions of source code must retain the above *copyright notice, this list of conditions and the following *disclaimer. * * - Redistributions in binary form must reproduce the above *copyright notice, this list of conditions and the following *disclaimer in the documentation and/or other materials *provided with the distribution. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS * BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN * ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE * SOFTWARE. */ #include ==> mst.h <== /* * Copyright (c) 2023 NVIDIA CORPORATION & AFFILIATES. ALL RIGHTS RESERVED. * * This software is available to you under a choice of one of two * licenses. You may choose to be licensed under the terms of the GNU * General Public License (GPL) Version 2, available from the file * COPYING in the main directory of this source tree, or the * OpenIB.org BSD license below: * * Redistribution and use in source and binary forms, with or * without modification, are permitted provided that the following * conditions are met: * * - Redistributions of source code must retain the above *copyright notice, this list of conditions and the following *disclaimer. * * - Redistributions in binary form must reproduce the above *copyright notice, this list of conditions and the following *disclaimer in the documentation and/or other materials *provided with the distribution. * * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, * EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND * NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS * BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN * ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE * SOFTWARE. */ #ifndef _MST_H_ ==> mst_kernel.h <== /* * Copyright (c) 2023 NVIDIA CORPORATION & AFFILIATES. ALL RIGHTS RESERVED. * * This software is available to you under a choice of one of two * licenses. You may choose to be licensed under the terms of the GNU * General Public License (GPL) Version 2, available from the file * COPYING in the main directory of this source tree, or the *
[Bug 2043098] Re: mstflint-dkms FTBS with linux 6.5 on jammy
# mantic verification Setting up mstflint-dkms (4.26.0+1-1ubuntu0.1) ... Loading new mstflint-4.26.0+1-1ubuntu0.1 DKMS files... Building for 6.5.0-28-generic Building initial module for 6.5.0-28-generic Secure Boot not enabled on this system. Done. mstflint_access.ko.zst: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.5.0-28-generic/updates/dkms/ depmod... Setting up g++ (4:13.2.0-1ubuntu1) ... update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode Setting up build-essential (12.10ubuntu1) ... Processing triggers for man-db (2.11.2-3) ... Processing triggers for libc-bin (2.38-1ubuntu6.2) ... needrestart is being skipped since dpkg has failed ubuntu@akis:~$ sudo modprobe mstflint_access ubuntu@akis:~$ lsmod | grep mstflint mstflint_access28672 0 ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043098 Title: mstflint-dkms FTBS with linux 6.5 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2043098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064535] [NEW] jammy update from 23.0.4 to 23.2.1 dropped transitional packages
Public bug reported: I happened to notice that the bump from 23.0.4 to 23.2.1 in jammy included a change that dropped a number of transitional packages: mesa (23.1.4-1) unstable; urgency=medium [ Diederik de Haas ] * Drop transitional libegl1-mesa package (Closes: #1032712) * Drop transitional libgles2-mesa package (Closes: #1032718) * Drop transitional libwayland-egl1-mesa package (Closes: #1032737) * Drop transitional libgl1-mesa-glx package (Closes: #1032738) * d/README.source: Update git repo location to Salsa Since I did not see that discussed in the SRU bug 2037604, I thought I'd call attention to it. No objection to this being closed as Won't Fix. I don't think this impacts any supported upgrade paths - focal GA'd w/ 20.0.4-2ubuntu1 which seems to have already had these transitional packages in place. This is presumably a practical regression for someone upgrading an old bionic install straight to jammy but that, of course, is not supported. ** Affects: mesa (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/2064535 Title: jammy update from 23.0.4 to 23.2.1 dropped transitional packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2064535/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: Backport iproute2 6.8.0 to noble
Hi Andrea - since this is now a stable release update, I *think* the
next steps should be:
1) Edit this bug to use the SRU Template
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template
(now done)
Since your team owns this package, please review that and let me know if you
have any concerns with that text.
2) Wait for 24.10 ('oracular') to open for devel and forcesync iproute2
w/ Debian
(https://wiki.ubuntu.com/StableReleaseUpdates#Development_Release_Fixed_First).
3) Upload the SRU, and wait for feedback from the sru team. If approved,
we'll need to run the tests in the [Test Case] section and make sure
there are no regressions from 6.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2051672
Title:
Backport iproute2 6.8.0 to noble
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: Backport iproute2 6.8.0 to noble
** Description changed: - iproute2 upstream produces releases coinciding with upstream kernel - releases to support the latest kernel features. Noble's iproute2 is - still back at v6.1 even though it will use the v6.8 kernel. This means - we provide no userspace interface for newer features - some of which are - noted by a networking hardware partner in bug 2060969. + [Impact] + Several networking features introduced in the upstream 6.2->6.8 kernels are not accessible to noble users because noble lacks the corresponding iproute2 update. This includes support for new hardware features such as per-VF offload settings (see bug 2060969), but many others that you can see in the attached changelogs. - Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu - FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no - longer needed, and we could now just do a merge. We could also port the - FAN patches forward if we can identify a need (see the original - description of this bug to a link to such a port), but I have not done - any testing with that. + Normally iproute2 is updated during the devel cycle to align with the + kernel version, but it was missed this cycle and discovered too late for + an FFe. We request an exception from the SRU team to do this as an SRU. + This includes dropping the Ubuntu Fan patches, which adds features to + iproute2 that no longer work since noble's kernels no longer support + Ubuntu Fan. - I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and - smoke tested it on an amd64 virtual machine: + [Test Case] + We'll run the 6.8 kernel self tests, which make use of a number of iproute2 features (see comment #17). NVIDIA's networking organization (Mellanox) has offered to put this through their QA process (details TBD). The upstream test suite will also run in the autopkgtests, though that suite is fairly stale. - ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb - (Reading database ... 83134 files and directories currently installed.) - Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ... - Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ... - dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d': Directory not empty - dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d': Directory not empty - dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not empty - Setting up iproute2 (6.8.0-1~24.04.1) ... - Removing obsolete conffile /etc/iproute2/group ... - Removing obsolete conffile /etc/iproute2/rt_realms ... - Removing obsolete conffile /etc/iproute2/rt_scopes ... - Removing obsolete conffile /etc/iproute2/rt_tables ... - Removing obsolete conffile /etc/iproute2/rt_tables.d/README ... - Removing obsolete conffile /etc/iproute2/rt_protos.d/README ... - Removing obsolete conffile /etc/iproute2/rt_protos ... - Removing obsolete conffile /etc/iproute2/rt_dsfield ... - Removing obsolete conffile /etc/iproute2/nl_protos ... - Removing obsolete conffile /etc/iproute2/ematch_map ... - Removing obsolete conffile /etc/iproute2/bpf_pinning ... - Processing triggers for man-db (2.12.0-4build1) ... + [What Could Go Wrong] + Users who may be running noble userspace with a non-noble kernel that supports Ubuntu Fan would lose support for configuring it. If the SRU team considers this to be a regression we should avoid, then we can add the Ubuntu Fan patches back. - The system rebooted fine. The ip command seems to behave normally. + iproute2 6.8 upstream retains backwards compatibility with earlier + releases (see comment #17). There are no commits with a Fixes: + annotation since the v6.8.0 tag was applied upstream. - Since the upstream test suite only appears to run at autopkgtest time, I triggered a run in my PPA, and it passed: - https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz + iproute2 is obviously a key package, and any upstream version bump + carries risk. This includes the possibility of breaking networking for + users of an Ubuntu LTS release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: Backport iproute2 6.8.0 to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: Backport iproute2 6.8.0 to noble
** Summary changed: - [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) + Backport iproute2 6.8.0 to noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: Backport iproute2 6.8.0 to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063950] Re: duplicate JsonCpp::JsonCpp leads to build failures
** Description changed: [Impact] Users trying to build software that links w/ jammy's libjsoncpp library will hit a build failure if that software uses cmake and another library that also requires libjsoncpp because libjsoncpp's cmake config does not protect against duplicate imports. This can be reproduced by building a a newer version of cmake itself using system libjsoncpp (I was trying to build 3.27.4, but I also checked that it impacts cmake master). [Test Case] This can be demonstrated by calling find_package twice in a row: $ mkdir test && cd test $ cat > CMakeLists.txt << EOF project(test) find_package(jsoncpp 1.9.5) find_package(jsoncpp 1.9.5) EOF $ cmake . -- The C compiler identification is GNU 11.4.0 -- The CXX compiler identification is GNU 11.4.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Error at /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncpp-namespaced-targets.cmake:5 (add_library): add_library cannot create imported target "JsonCpp::JsonCpp" because another target with the same name already exists. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncppConfig.cmake:41 (include) CMakeLists.txt:3 (find_package) CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 3.22) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP". This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring incomplete, errors occurred! See also "/home/ubuntu/test/CMakeFiles/CMakeOutput.log". + [Fix] + Backport a fix from mantic that adds a guard in the .cmake file. + [ What Could Go Wrong ] We could cause reverse dependencies to fail to build from source due to an inadvertent error. We can mitigate this by doing a test rebuild of the reverse dependencies, which I've done in a PPA: - https://launchpad.net/~dannf/+archive/ubuntu/libjsoncpp-sru-test/+packages + https://launchpad.net/~dannf/+archive/ubuntu/libjsoncpp-sru-test/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063950 Title: duplicate JsonCpp::JsonCpp leads to build failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/2063950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063950] Re: duplicate JsonCpp::JsonCpp leads to build failures
** Description changed: [Impact] Users trying to build software that links w/ jammy's libjsoncpp library will hit a build failure if that software uses cmake and another library that also requires libjsoncpp because libjsoncpp's cmake config does not protect against duplicate imports. This can be reproduced by building a a newer version of cmake itself using system libjsoncpp (I was trying to build 3.27.4, but I also checked that it impacts cmake master). [Test Case] This can be demonstrated by calling find_package twice in a row: $ mkdir test && cd test $ cat > CMakeLists.txt << EOF project(test) find_package(jsoncpp 1.9.5) find_package(jsoncpp 1.9.5) EOF $ cmake . -- The C compiler identification is GNU 11.4.0 -- The CXX compiler identification is GNU 11.4.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Error at /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncpp-namespaced-targets.cmake:5 (add_library): add_library cannot create imported target "JsonCpp::JsonCpp" because another target with the same name already exists. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncppConfig.cmake:41 (include) CMakeLists.txt:3 (find_package) CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 3.22) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP". This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring incomplete, errors occurred! See also "/home/ubuntu/test/CMakeFiles/CMakeOutput.log". [ What Could Go Wrong ] - We could cause reverse dependencies to fail to build from source due to an inadvertent error. We can mitigate this by doing a test rebuild of the reverse dependencies. + We could cause reverse dependencies to fail to build from source due to an inadvertent error. We can mitigate this by doing a test rebuild of the reverse dependencies, which I've done in a PPA: + https://launchpad.net/~dannf/+archive/ubuntu/libjsoncpp-sru-test/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063950 Title: duplicate JsonCpp::JsonCpp leads to build failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/2063950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063950] Re: duplicate JsonCpp::JsonCpp leads to build failures
** Description changed: [Impact] - Users trying to build software that links w/ jammy's libjsoncpp library will hit a build failure if that software uses cmake and another library that also requires libjsoncpp. This can be reproduced by building a a new version of cmake itself (reproduced w/ today's master, as well as going back to the 3.27.4 release). + Users trying to build software that links w/ jammy's libjsoncpp library will hit a build failure if that software uses cmake and another library that also requires libjsoncpp because libjsoncpp's cmake config does not protect against duplicate imports. This can be reproduced by building a a newer version of cmake itself using system libjsoncpp (I was trying to build 3.27.4, but I also checked that it impacts cmake master). [Test Case] This can be demonstrated by calling find_package twice in a row: $ mkdir test && cd test $ cat > CMakeLists.txt << EOF project(test) find_package(jsoncpp 1.9.5) find_package(jsoncpp 1.9.5) EOF $ cmake . -- The C compiler identification is GNU 11.4.0 -- The CXX compiler identification is GNU 11.4.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Error at /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncpp-namespaced-targets.cmake:5 (add_library): - add_library cannot create imported target "JsonCpp::JsonCpp" because - another target with the same name already exists. + add_library cannot create imported target "JsonCpp::JsonCpp" because + another target with the same name already exists. Call Stack (most recent call first): - /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncppConfig.cmake:41 (include) - CMakeLists.txt:3 (find_package) - + /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncppConfig.cmake:41 (include) + CMakeLists.txt:3 (find_package) CMake Warning (dev) in CMakeLists.txt: - No cmake_minimum_required command is present. A line of code such as + No cmake_minimum_required command is present. A line of code such as - cmake_minimum_required(VERSION 3.22) + cmake_minimum_required(VERSION 3.22) - should be added at the top of the file. The version specified may be lower - if you wish to support older CMake versions for this project. For more - information run "cmake --help-policy CMP". + should be added at the top of the file. The version specified may be lower + if you wish to support older CMake versions for this project. For more + information run "cmake --help-policy CMP". This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring incomplete, errors occurred! See also "/home/ubuntu/test/CMakeFiles/CMakeOutput.log". - [ What Could Go Wrong ] We could cause reverse dependencies to fail to build from source due to an inadvertent error. We can mitigate this by doing a test rebuild of the reverse dependencies. ** Also affects: libjsoncpp (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: libjsoncpp (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: libjsoncpp (Ubuntu Noble) Status: New => Fix Released ** Changed in: libjsoncpp (Ubuntu Mantic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063950 Title: duplicate JsonCpp::JsonCpp leads to build failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/2063950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063950] [NEW] duplicate JsonCpp::JsonCpp leads to build failures
Public bug reported: [Impact] Users trying to build software that links w/ jammy's libjsoncpp library will hit a build failure if that software uses cmake and another library that also requires libjsoncpp because libjsoncpp's cmake config does not protect against duplicate imports. This can be reproduced by building a a newer version of cmake itself using system libjsoncpp (I was trying to build 3.27.4, but I also checked that it impacts cmake master). [Test Case] This can be demonstrated by calling find_package twice in a row: $ mkdir test && cd test $ cat > CMakeLists.txt << EOF project(test) find_package(jsoncpp 1.9.5) find_package(jsoncpp 1.9.5) EOF $ cmake . -- The C compiler identification is GNU 11.4.0 -- The CXX compiler identification is GNU 11.4.0 -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Error at /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncpp-namespaced-targets.cmake:5 (add_library): add_library cannot create imported target "JsonCpp::JsonCpp" because another target with the same name already exists. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/jsoncpp/jsoncppConfig.cmake:41 (include) CMakeLists.txt:3 (find_package) CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 3.22) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP". This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring incomplete, errors occurred! See also "/home/ubuntu/test/CMakeFiles/CMakeOutput.log". [ What Could Go Wrong ] We could cause reverse dependencies to fail to build from source due to an inadvertent error. We can mitigate this by doing a test rebuild of the reverse dependencies. ** Affects: libjsoncpp (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: libjsoncpp (Ubuntu Jammy) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: libjsoncpp (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Affects: libjsoncpp (Ubuntu Noble) Importance: Undecided Status: Fix Released ** Also affects: libjsoncpp (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libjsoncpp (Ubuntu Jammy) Status: New => In Progress ** Changed in: libjsoncpp (Ubuntu Jammy) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063950 Title: duplicate JsonCpp::JsonCpp leads to build failures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjsoncpp/+bug/2063950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
On Mon, Apr 22, 2024 at 11:07:54AM -, Matthieu Baerts wrote: > > I don't think we can justify dropping FAN support in an SRU, so let's > add that port back in. > > Even if it will not be used in Ubuntu 24.04, I'm happy to drop it if the stable release team would accept it. Here's the policy: https://wiki.ubuntu.com/StableReleaseUpdates However, I don't see how we can argue that dropping FAN support is *not* a regression, even if the kernel we ship does not support it. > and dropping these patches would stop the diversion with Debian? That's not a goal of our SRU process. We can always realign with Debian during the next devel cycle. > > @matttbe - is there any documentation about upstream compatibility > > guarantees and regression testing done that you're aware of, or any tests > > that we could run beyond those in our autopkgtests? > > @dannf: IPRoute2 is following the kernel development, and it is not > supposed to break the compatibility with older kernel versions (also > because the kernel's user API is not supposed to break). > > There is a test suite included in the source code, but it looks like it > is not tested when building the .deb package, check the 'debian/rules' > file: > > override_dh_auto_test: > # upstream test suite needs root and leaves machine unclean, skip > it The package does seem to include this in its autopkgtests (debian/tests/testsuite.sh), so I think we have that coverage. > > I never used it, (and it looks like it is not often updated), but IPRoute2 > (ip, tc, ss, etc.) is also heavily used in the kernel selftests: > > $ git grep -cw -e ip -e tc -e ss -- tools/testing/selftests/ | wc -l > 635 > > Maybe these tests are already being validated when building a new kernel for > Ubuntu? That's another way to validate IPRoute2. Thanks for the pointer! -dann > Other than that, Debian is using IPRoute2 versions > 6.1 for a long time > now. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
Thank Utkarsh. Yeah, we just dropped the ball on not getting this done sooner. I'd like to see if we can make the case for SRU'ing 6.8 in, so let's convert the bug to that. I don't think we can justify dropping FAN support in an SRU, so let's add that port back in. We'll need to make a convincing case to the SRU team that the risk of regression is minimal. Our partners at NVIDIA/Mellanox have offered to put this release through their testing. I'll see if they can provide details on what their tests will cover. @matttbe - is there any documentation about upstream compatibility guarantees and regression testing done that you're aware of, or any tests that we could run beyond those in our autopkgtests? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060969] Re: UB 24.04: update uproute2 package
*** This bug is a duplicate of bug 2051672 *** https://bugs.launchpad.net/bugs/2051672 Amir - we're working on this in bug 2051672, and I subscribed you to it. I have prepared a build of iproute2 6.8 for noble in a PPA: https://launchpad.net/~dannf/+archive/ubuntu/test If there is some testing you can do with it to help validate it, that would be appreciated. Please update bug 2051672 with any results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060969 Title: UB 24.04: update uproute2 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051571] Re: jammy: 4.21.0-7 dropped mstlink binary
** Description changed: - Both jammy's previous 4.17.0+1-1build2 and noble's recent 4.26.0+1-2 - include it, and 4.21.0-7 itself continues to ship its manpage. + [Impact] + The mstlink and mstreg binaries have regressed in the last jammy update. This is because a new upstream landed in jammy as an SRU, but is based on upstream's debian/ packaging, not Debian's, which enable different build flags. - There isn't any indication in the changelog of a reason for dropping it. + [Test Case] + /usr/bin/mstlink and /usr/bin/mstreg have returned. + + [What Could Go Wrong] + While this update does restore files that were dropped in the last "SRU", it does drop some files that the Debian packaging does not ship. This includes some header files, some .a files, and 2 manpages for binaries that neither version of the package ships. + + It is possible that somebody has started using these files, and by + taking them away we break someone. That seems unlikely - these appear to + be for internal-use only. + + Here's a complete diff: + + --- mstflint.jammy.orig 2024-04-12 21:40:42.700199967 + + +++ mstflint.jammy.ppa2024-04-12 21:58:59.495997299 + + @@ -6,37 +6,20 @@ + /usr/bin/mstflint + /usr/bin/mstfwreset + /usr/bin/mstfwtrace + +/usr/bin/mstlink + /usr/bin/mstmcra + /usr/bin/mstmread + /usr/bin/mstmtserver + /usr/bin/mstmwrite + /usr/bin/mstprivhost + +/usr/bin/mstreg + /usr/bin/mstregdump + /usr/bin/mstresourcedump + /usr/bin/mstresourceparse + /usr/bin/mstvpd + -/usr/include + -/usr/include/mstflint + -/usr/include/mstflint/cmdif + -/usr/include/mstflint/cmdif/icmd_cif_common.h + -/usr/include/mstflint/cmdif/icmd_cif_open.h + -/usr/include/mstflint/common + -/usr/include/mstflint/common/compatibility.h + -/usr/include/mstflint/mtcr.h + -/usr/include/mstflint/mtcr_com_defs.h + -/usr/include/mstflint/mtcr_mf.h + -/usr/include/mstflint/tools_layouts + -/usr/include/mstflint/tools_layouts/adb_to_c_utils.h + -/usr/include/mstflint/tools_layouts/icmd_layouts.h + -/usr/include/mtcr_ul + /usr/lib + /usr/lib/x86_64-linux-gnu + -/usr/lib/x86_64-linux-gnu/libcmdif.a + -/usr/lib/x86_64-linux-gnu/libdev_mgt.a + -/usr/lib/x86_64-linux-gnu/libreg_access.a + -/usr/lib/x86_64-linux-gnu/libtools_layouts.a + /usr/lib/x86_64-linux-gnu/mstflint + -/usr/lib/x86_64-linux-gnu/mstflint/libmtcr_ul.a + /usr/lib/x86_64-linux-gnu/mstflint/python_tools + /usr/lib/x86_64-linux-gnu/mstflint/python_tools/c_dev_mgt.so + /usr/lib/x86_64-linux-gnu/mstflint/python_tools/ccmdif.so + @@ -150,13 +133,14 @@ + /usr/share/doc/mstflint/README.gz + /usr/share/doc/mstflint/changelog.Debian.gz + /usr/share/doc/mstflint/copyright + +/usr/share/lintian + +/usr/share/lintian/overrides + +/usr/share/lintian/overrides/mstflint + /usr/share/man + /usr/share/man/man1 + -/usr/share/man/man1/mstarchive.1.gz + /usr/share/man/man1/mstconfig.1.gz + /usr/share/man/man1/mstcongestion.1.gz + /usr/share/man/man1/mstflint.1.gz + -/usr/share/man/man1/mstfwmanager.1.gz + /usr/share/man/man1/mstfwreset.1.gz + /usr/share/man/man1/mstfwtrace.1.gz + /usr/share/man/man1/mstlink.1.gz + @@ -196,6 +180,10 @@ + /usr/share/mstflint/mlxconfig_dbs + /usr/share/mstflint/mlxconfig_dbs/mlxconfig_host.db + /usr/share/mstflint/mlxconfig_dbs/mlxconfig_switch.db + -/usr/include/mtcr_ul/mtcr.h + -/usr/include/mtcr_ul/mtcr_com_defs.h + -/usr/lib/libmtcr_ul.a + +/usr/share/mstflint/prm_dbs + +/usr/share/mstflint/prm_dbs/hca + +/usr/share/mstflint/prm_dbs/hca/ext + +/usr/share/mstflint/prm_dbs/hca/ext/register_access_table.adb + +/usr/share/mstflint/prm_dbs/switch + +/usr/share/mstflint/prm_dbs/switch/ext + +/usr/share/mstflint/prm_dbs/switch/ext/register_access_table.adb ** Description changed: [Impact] - The mstlink and mstreg binaries have regressed in the last jammy update. This is because a new upstream landed in jammy as an SRU, but is based on upstream's debian/ packaging, not Debian's, which enable different build flags. + The mstlink and mstreg binaries have regressed in the last jammy update. This is because a new upstream landed in jammy as an SRU outside of the SRU process, and is based on upstream's debian/ packaging, not Debian's, which enable different build flags. [Test Case] /usr/bin/mstlink and /usr/bin/mstreg have returned. [What Could Go Wrong] While this update does restore files that were dropped in the last "SRU", it does drop some files that the Debian packaging does not ship. This includes some header files, some .a files, and 2 manpages for binaries that neither version of the package ships. It is possible that somebody has started using these files, and by taking them away we break someone. That seems unlikely - these appear to be for internal-use only. Here's a complete diff: --- mstflint.jammy.orig 2024-04-12 21:40:42.700199967 + +++ mstflint.jammy.ppa2024-04-12 21:58:59.495997299 + @@ -6,37 +6,20 @@ - /usr/bin/mstflint -
[Bug 2061185] Re: mstflint-dkms module bug causes UBSAN errors in dmesg
** Description changed: [Impact] A bug in the kernel module source can cause error messages to show up in the kernel when an application closes the device when UBSAN is active. + + From an NVIDIA DGX 1 system: + $ sudo mstflint -d 84:00.0 q + $ dmesg + [ 304.400217] + [ 304.400267] UBSAN: shift-out-of-bounds in /var/lib/dkms/mstflint/4.21.0-7/build/mst_main.c:601:21 + [ 304.400283] shift exponent 4294967295 is too large for 32-bit type 'int' + [ 304.400295] CPU: 65 PID: 25268 Comm: mstflint Tainted: G OE 5.15.0-102-generic #112-Ubuntu + [ 304.400298] Hardware name: NVIDIA DGX-1 with V100-32/DGX-1 with V100-32, BIOS S2W_3A13 01/03/2023 + [ 304.400299] Call Trace: + [ 304.400301] + [ 304.400303] show_stack+0x52/0x5c + [ 304.400309] dump_stack_lvl+0x4a/0x63 + [ 304.400315] dump_stack+0x10/0x16 + [ 304.400318] ubsan_epilogue+0x9/0x36 + [ 304.400320] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef + [ 304.400324] ? do_sigaction+0x226/0x290 + [ 304.400329] mst_release.cold+0x14/0x26 [mstflint_access] + [ 304.400332] __fput+0x9f/0x280 + [ 304.400338] fput+0xe/0x20 + [ 304.400340] task_work_run+0x6d/0xb0 + [ 304.400345] exit_to_user_mode_loop+0x157/0x160 + [ 304.400352] exit_to_user_mode_prepare+0xa0/0xb0 + [ 304.400354] syscall_exit_to_user_mode+0x27/0x50 + [ 304.400372] ? __x64_sys_close+0x11/0x50 + [ 304.400375] do_syscall_64+0x69/0xc0 + [ 304.400380] ? do_syscall_64+0x69/0xc0 + [ 304.400383] ? do_syscall_64+0x69/0xc0 + [ 304.400385] entry_SYSCALL_64_after_hwframe+0x62/0xcc + [ 304.400389] RIP: 0033:0x7f0347edaf67 + [ 304.400391] Code: ff e8 0d 16 02 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 41 c3 48 83 ec 18 89 7c 24 0c e8 73 ba f7 ff + [ 304.400393] RSP: 002b:7ffebcd12c98 EFLAGS: 0246 ORIG_RAX: 0003 + [ 304.400396] RAX: RBX: 55aa91e5fe10 RCX: 7f0347edaf67 + [ 304.400398] RDX: RSI: 55aa913737a1 RDI: 0003 + [ 304.400399] RBP: 55aa91e5fe10 R08: 55aa91e60cc0 R09: 55aa91e61160 + [ 304.400400] R10: 55aa91e615b0 R11: 0246 R12: 55aa91e60820 + [ 304.400401] R13: 55aa91e2b650 R14: 55aa91e4b3f0 R15: 55aa9136ac47 + [ 304.400403] + [ 304.400404] + [Test Case] Load the mstflint_access module open then close a /dev/*_mstconf file Look for any errors in dmesg [What Could Go Wrong] A severe bug in the fix could cause the problem to escalate to an oops or panic. ** Description changed: [Impact] - A bug in the kernel module source can cause error messages to show up in the kernel when an application closes the device when UBSAN is active. + A bug in the kernel module source can cause error messages to show up in the kernel when an application closes the device when UBSAN is active. This is likely to cause unnecessary user worry: From an NVIDIA DGX 1 system: $ sudo mstflint -d 84:00.0 q $ dmesg [ 304.400217] [ 304.400267] UBSAN: shift-out-of-bounds in /var/lib/dkms/mstflint/4.21.0-7/build/mst_main.c:601:21 [ 304.400283] shift exponent 4294967295 is too large for 32-bit type 'int' [ 304.400295] CPU: 65 PID: 25268 Comm: mstflint Tainted: G OE 5.15.0-102-generic #112-Ubuntu [ 304.400298] Hardware name: NVIDIA DGX-1 with V100-32/DGX-1 with V100-32, BIOS S2W_3A13 01/03/2023 [ 304.400299] Call Trace: [ 304.400301] [ 304.400303] show_stack+0x52/0x5c [ 304.400309] dump_stack_lvl+0x4a/0x63 [ 304.400315] dump_stack+0x10/0x16 [ 304.400318] ubsan_epilogue+0x9/0x36 [ 304.400320] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef [ 304.400324] ? do_sigaction+0x226/0x290 [ 304.400329] mst_release.cold+0x14/0x26 [mstflint_access] [ 304.400332] __fput+0x9f/0x280 [ 304.400338] fput+0xe/0x20 [ 304.400340] task_work_run+0x6d/0xb0 [ 304.400345] exit_to_user_mode_loop+0x157/0x160 [ 304.400352] exit_to_user_mode_prepare+0xa0/0xb0 [ 304.400354] syscall_exit_to_user_mode+0x27/0x50 [ 304.400372] ? __x64_sys_close+0x11/0x50 [ 304.400375] do_syscall_64+0x69/0xc0 [ 304.400380] ? do_syscall_64+0x69/0xc0 [ 304.400383] ? do_syscall_64+0x69/0xc0 [ 304.400385] entry_SYSCALL_64_after_hwframe+0x62/0xcc [ 304.400389] RIP: 0033:0x7f0347edaf67 [ 304.400391] Code: ff e8 0d 16 02 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 41 c3 48 83 ec 18 89 7c 24 0c e8 73 ba f7 ff [ 304.400393] RSP: 002b:7ffebcd12c98 EFLAGS: 0246 ORIG_RAX: 0003 [ 304.400396] RAX:
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
** Description changed: iproute2 upstream produces releases coinciding with upstream kernel releases to support the latest kernel features. Noble's iproute2 is still back at v6.1 even though it will use the v6.8 kernel. This means we provide no userspace interface for newer features - some of which are noted by a networking hardware partner in bug 2060969. Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no longer needed, and we could now just do a merge. We could also port the FAN patches forward if we can identify a need (see the original description of this bug to a link to such a port), but I have not done any testing with that. I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and smoke tested it on an amd64 virtual machine: - ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb + ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb (Reading database ... 83134 files and directories currently installed.) Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ... Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ... dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d': Directory not empty dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not empty Setting up iproute2 (6.8.0-1~24.04.1) ... Removing obsolete conffile /etc/iproute2/group ... Removing obsolete conffile /etc/iproute2/rt_realms ... Removing obsolete conffile /etc/iproute2/rt_scopes ... Removing obsolete conffile /etc/iproute2/rt_tables ... Removing obsolete conffile /etc/iproute2/rt_tables.d/README ... Removing obsolete conffile /etc/iproute2/rt_protos.d/README ... Removing obsolete conffile /etc/iproute2/rt_protos ... Removing obsolete conffile /etc/iproute2/rt_dsfield ... Removing obsolete conffile /etc/iproute2/nl_protos ... Removing obsolete conffile /etc/iproute2/ematch_map ... Removing obsolete conffile /etc/iproute2/bpf_pinning ... Processing triggers for man-db (2.12.0-4build1) ... The system rebooted fine. The ip command seems to behave normally. + + Since the upstream test suite only appears to run at autopkgtest time, I triggered a run in my PPA, and it passed: + https://autopkgtest.ubuntu.com/results/autopkgtest-noble-dannf-test/noble/amd64/i/iproute2/20240412_210819_97417@/log.gz ** Changed in: iproute2 (Ubuntu) Milestone: ubuntu-24.04-beta => ubuntu-24.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061186] [NEW] mstflint_access kernel module licensing is inconsistent
Public bug reported: [Impact] The mstflint_access kernel module provided by the mstflint-dkms package has inconsistent licensing in the source. While the SPDX-License-Identifier tag says "GPL-2.0 or Linux-OpenIB", the license header only lists BSD-3-Clause, which covers the Linux OpenIB license, but not the GPL. Since I'm backporting changes before/after this correction, I felt it made sense to backport the licensing clarification as well. [Test Case] Confirm that the licensing in the source is now consistent. [Where Things Could Go Wrong] This is self-described as a licensing correct - updating comments only. ** Affects: mstflint (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mstflint (Ubuntu Jammy) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: mstflint (Ubuntu Mantic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: mstflint (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: mstflint (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mstflint (Ubuntu) Status: New => Fix Released ** Summary changed: - mstflint licensing is unclear + mstflint_access kernel module licensing is unclear ** Summary changed: - mstflint_access kernel module licensing is unclear + mstflint_access kernel module licensing is inconsistent ** Changed in: mstflint (Ubuntu Jammy) Status: New => In Progress ** Changed in: mstflint (Ubuntu Mantic) Status: New => In Progress ** Changed in: mstflint (Ubuntu Jammy) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: mstflint (Ubuntu Mantic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061186 Title: mstflint_access kernel module licensing is inconsistent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2061186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061185] [NEW] mstflint-dkms module bug causes UBSAN errors in dmesg
Public bug reported: [Impact] A bug in the kernel module source can cause error messages to show up in the kernel when an application closes the device when UBSAN is active. [Test Case] Load the mstflint_access module open then close a /dev/*_mstconf file Look for any errors in dmesg [What Could Go Wrong] A severe bug in the fix could cause the problem to escalate to an oops or panic. ** Affects: mstflint (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mstflint (Ubuntu Jammy) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: mstflint (Ubuntu Mantic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: mstflint (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mstflint (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: mstflint (Ubuntu) Status: New => Fix Released ** Changed in: mstflint (Ubuntu Mantic) Status: New => In Progress ** Changed in: mstflint (Ubuntu Jammy) Status: New => In Progress ** Changed in: mstflint (Ubuntu Jammy) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: mstflint (Ubuntu Mantic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061185 Title: mstflint-dkms module bug causes UBSAN errors in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2061185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043098] Re: mstflint-dkms FTBS with linux 6.5 on jammy
** Also affects: mstflint (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: mstflint (Ubuntu Mantic) Status: New => In Progress ** Changed in: mstflint (Ubuntu Mantic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043098 Title: mstflint-dkms FTBS with linux 6.5 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2043098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061182] Re: mstflint-dkms no longer exists in mantic
** Description changed: [Impact] Users upgrading from jammy to mantic will not have an mstflint-dkms package. This will leave the mstflint-dkms package from jammy installed, which is incompatible with the 6.5 kernel. - The reason we ended up here was due to a bypass of the SRU process, described here: + The mstflint 4.21 package in mantic includes the kernel module source - it just doesn't build the mstflint-dkms package. The reason we ended up here was due to a bypass of the SRU process, described here: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2051571/comments/1 + mstflint 4.21's kernel source does not build with the 6.5 kernel in + mantic. For that we need the 4.26 source. I looked at backporting + src:mstflint 4.26 from noble in its entirety to resolve this issue, but + aborted after finding a backwards compatibility issue in the mstflint + deb (bug 2060026). + + Instead, I'm looking to backport only the dkms changes from 4.26 into + 4.21. + + Now, this may seem like a lot to do for an obscure package in an interim + release. But this is just a precursor to resolving bug 2051571 in jammy, + which I expect to be a simple backport of the mantic SRU to jammy. + [Test Case] - mstflint-dkms installs in mantic and builds against the mantic kernel. Also, mstflint-dkms/mantic upgrades cleanly from jammy. + - mstflint-dkms installs in mantic and builds against the mantic kernel. + - mstflint-dkms/mantic upgrades cleanly from jammy. + - mstflint-dkms/mantic upgrades cleanly to noble. Regression test: compare the contents of the mstflint binary package before/after, makes sure the file list matches and maintainer scripts are equivalent. [What Could Go Wrong] - Introducing the mstflint-dkms package should carry a low regression risk because the package does not already exist in mantic. However, the packaging changes could introduce regressions in the other binary package, mstflint, if they are buggy. + Introducing the mstflint-dkms package should carry a low regression risk because the package does not already exist in mantic. However, the packaging changes could introduce regressions in the other binary package, mstflint, if they are buggy. The upstream version bump of the mstflint-dkms package needs to be handled carefully, or we'll risk breaking ** Changed in: mstflint (Ubuntu Mantic) Status: New => In Progress ** Changed in: mstflint (Ubuntu Mantic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: mstflint (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061182 Title: mstflint-dkms no longer exists in mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2061182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061182] [NEW] mstflint-dkms no longer exists in mantic
Public bug reported: [Impact] Users upgrading from jammy to mantic will not have an mstflint-dkms package. This will leave the mstflint-dkms package from jammy installed, which is incompatible with the 6.5 kernel. The reason we ended up here was due to a bypass of the SRU process, described here: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2051571/comments/1 [Test Case] mstflint-dkms installs in mantic and builds against the mantic kernel. Also, mstflint-dkms/mantic upgrades cleanly from jammy. Regression test: compare the contents of the mstflint binary package before/after, makes sure the file list matches and maintainer scripts are equivalent. [What Could Go Wrong] Introducing the mstflint-dkms package should carry a low regression risk because the package does not already exist in mantic. However, the packaging changes could introduce regressions in the other binary package, mstflint, if they are buggy. ** Affects: mstflint (Ubuntu) Importance: Undecided Status: New ** Affects: mstflint (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: mstflint (Ubuntu Mantic) 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/2061182 Title: mstflint-dkms no longer exists in mantic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2061182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060026] Re: backport 4.26.0 to jammy
I found that the mstflint command has dropped some command line parameters in 4.26.0 (--private-key-label, --public-key-label, --hsm), so that has more regression potential. For now, I'm moving to Won't Fix. ** Changed in: mstflint (Ubuntu Jammy) Status: In Progress => Won't Fix ** Changed in: mstflint (Ubuntu Mantic) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060026 Title: backport 4.26.0 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2060026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
** Description changed: - A few versions have been released and Ubuntu Noble still has the 6.1 - version (6.1.0-1ubuntu2) from one year ago. Could it be possible to - import the latest version from Debian unstable fixing a bunch of issues - and supporting features from more recent kernels? + iproute2 upstream produces releases coinciding with upstream kernel + releases to support the latest kernel features. Noble's iproute2 is + still back at v6.1 even though it will use the v6.8 kernel. This means + we provide no userspace interface for newer features - some of which are + noted by a networking hardware partner in bug 2060969. - Please note that Ubuntu Noble 24.04 will probably be shipped with the - v6.8 kernel [1]. IPRoute v6.1 supports features added up to the v6.1 - kernel, so missing the ones added to earlier versions. Switching to the - v6.7 now should ease the upgrade to the v6.8 later. + Ubuntu's iproute2 has diverged from Debian's to add support for Ubuntu + FAN. Noble has dropped kernel support for Ubuntu FAN, so those are no + longer needed, and we could now just do a merge. We could also port the + FAN patches forward if we can identify a need (see the original + description of this bug to a link to such a port), but I have not done + any testing with that. - [1] https://discourse.ubuntu.com/t/introducing-kernel-6-8-for- - the-24-04-noble-numbat-release/41958 + I have built Debian's iproute2 in a noble ppa at ppa:dannf/test and + smoke tested it on an amd64 virtual machine: - Upstream ChangeLog: + ubuntu@cortez-vm-0:~$ sudo dpkg -i iproute2_6.8.0-1~24.04.1_amd64.deb + (Reading database ... 83134 files and directories currently installed.) + Preparing to unpack iproute2_6.8.0-1~24.04.1_amd64.deb ... + Unpacking iproute2 (6.8.0-1~24.04.1) over (6.1.0-1ubuntu6) ... + dpkg: warning: unable to delete old directory '/etc/iproute2/rt_tables.d': Directory not empty + dpkg: warning: unable to delete old directory '/etc/iproute2/rt_protos.d': Directory not empty + dpkg: warning: unable to delete old directory '/etc/iproute2': Directory not empty + Setting up iproute2 (6.8.0-1~24.04.1) ... + Removing obsolete conffile /etc/iproute2/group ... + Removing obsolete conffile /etc/iproute2/rt_realms ... + Removing obsolete conffile /etc/iproute2/rt_scopes ... + Removing obsolete conffile /etc/iproute2/rt_tables ... + Removing obsolete conffile /etc/iproute2/rt_tables.d/README ... + Removing obsolete conffile /etc/iproute2/rt_protos.d/README ... + Removing obsolete conffile /etc/iproute2/rt_protos ... + Removing obsolete conffile /etc/iproute2/rt_dsfield ... + Removing obsolete conffile /etc/iproute2/nl_protos ... + Removing obsolete conffile /etc/iproute2/ematch_map ... + Removing obsolete conffile /etc/iproute2/bpf_pinning ... + Processing triggers for man-db (2.12.0-4build1) ... - - 6.2: https://lore.kernel.org/netdev/20230220105811.674bd304@hermes.local/ - - 6.3: https://lore.kernel.org/netdev/20230427090253.7a92616b@hermes.local/ - - 6.4: https://lore.kernel.org/netdev/20230626093137.2f302acc@hermes.local/ - - 6.5: https://lore.kernel.org/netdev/20230906093918.394a1b1d@hermes.local/ - - 6.6: https://lore.kernel.org/netdev/20231106090325.07092c87@hermes.local/ - - 6.7: https://lore.kernel.org/netdev/20240108094709.050e22bc@hermes.local/ - - 6.8: https://lore.kernel.org/netdev/20240311094432.16bf9516@hermes.local/ - - (Previous changelog: - https://lore.kernel.org/netdev/?q=s%3A%22%5BANNOUNCE%5D+iproute2%22+AND+NOT+s%3A%22Re%3A%22 - ) - - ChangeLog from Debian: - - iproute2 (6.8.0-1) unstable; urgency=medium - - [ Ceppo ] - * Update Italian po-debconf translation (Closes: #1063002) - - [ Luca Boccassi ] - * Add build dependency on libnsl-dev (Closes: #1065214) - * Switch to pkgconf - * Update upstream source from tag 'upstream/6.8.0' - * Drop 0002-ss-show-extra-info-when-processes-is-not-used.patch, merged - upstream - * Drop iproute2-doc package - * Drop tc/m_xt.so and tc/m_ipt.so, removed upstream - - -- Luca Boccassi <> Tue, 12 Mar 2024 14:02:38 + - - iproute2 (6.7.0-2) unstable; urgency=medium - - * Backport fix for 'ss' output - - -- Luca Boccassi <> Mon, 22 Jan 2024 12:24:29 + - - iproute2 (6.7.0-1) unstable; urgency=medium - - * Add Italian debconf translation (Closes: #1056582) - * Update upstream source from tag 'upstream/6.7.0' - * Bump copyright year ranges in d/copyright - * Drop 0002-Revert-Makefile-ensure-CONF_USR_DIR-honours-the-libd.patch, - merged upstream - * Default config files moved from /usr/lib to /usr/share - - -- Luca Boccassi <> Fri, 12 Jan 2024 21:47:59 + - - iproute2 (6.6.0-1) unstable; urgency=medium - - * Update upstream source from tag 'upstream/6.6.0' - * Backport patch to fix configuration installation - * Remove handling of qt_atm.so, dropped upstream - - -- Luca Boccassi <> Sun, 05 Nov 2023 22:46:20 + - - iproute2 (6.5.0-5) unstable; urgency=medium - - * Use
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
Thanks Matthieu. I spoke to the kernel team and I think they will handle the update. I'm just trying to help unblock them by getting this reviewed/agreed by our release team ahead of time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
** Attachment added: "Upstream 6.7 changelog" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763789/+files/6.7-changes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
** Attachment added: "Upstream 6.8 changelog" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763790/+files/6.8-changes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
** Attachment added: "Upstream 6.4 changelog" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763786/+files/6.4-changes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
** Attachment added: "Upstream 6.6 changelog" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763788/+files/6.6-changes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
** Attachment added: "Upstream 6.5 changelog" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763787/+files/6.5-changes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
** Attachment added: "Upstream 6.3 changelog" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763785/+files/6.3-changes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
It seems like this bug should now be a FFe (see https://wiki.ubuntu.com/FreezeExceptionProcess) - so converting... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
** Attachment added: "Upstream 6.2 changelog" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+attachment/5763784/+files/6.2-changes.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051672] Re: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main)
** Summary changed: - Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) + [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051672 Title: [FFe] Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2051672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060969] Re: UB 24.04: update uproute2 package
*** This bug is a duplicate of bug 2051672 *** https://bugs.launchpad.net/bugs/2051672 ** This bug has been marked a duplicate of bug 2051672 Merge iproute2 with the latest Debian version: 6.8.0-1 from testing/unstable (main) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060969 Title: UB 24.04: update uproute2 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058557] Re: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel
** Changed in: linux (Ubuntu) Assignee: Jose Ogando Justo (joseogando) => Mitchell Augustin (mitchellaugustin) ** Changed in: linux (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058557 Title: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060026] [NEW] backport 4.26.0 to jammy
Public bug reported: [Impact] This release contains both bug-fixes, new hardware support, and new features for users of Mellanox network controllers. Some examples are: 9bb8d2c8 Fix MaskBootRecordCRC for CX8 3269c0a0 Support GPIO toggling for BF3 same as CX 058537c5 Some CX-7 devices information did not show up when running the query utility mlxfwmanager. f7534912 [flint][mflash] Support new seventh gen flash for QT3/CX8/BF4 It also addresses: * mstflint-dkms in jammy does not build against the 6.5 kernel (bug 2043098) * jammy: 4.21.0-7 dropped mstlink binary (bug 2051571) [Test Case] The following development and SRU process will be followed: https://wiki.ubuntu.com/mstflint-Updates Note: I drafted that to request an SRU special case, but the SRU team decided to approve the backport I was doing at that time (bug 1864475) as a one-off instead of granting a special case. [Regression Potential] In order to mitigate the regression potential, the aforementioned testing will be performed. The results of that testing, delineated in the following checklist, will be captured in this bug prior to adding the verification-done tag: [ ] Verified that all of the utilities from the current version in this series are still present in the new version. [ ] Verified that the supported flags for each utility in the new version, as described in --help output, are a superset of the existing version in this series. [ ] The existing version of mstflint upgrades cleanly to the new version. [ ] Mellanox has executed their mstflint test plan, and results are uploaded to this bug for each series. ** Affects: mstflint (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mstflint (Ubuntu Jammy) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: mstflint (Ubuntu Mantic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: mstflint (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mstflint (Ubuntu) Status: New => Fix Released ** Also affects: mstflint (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: mstflint (Ubuntu Jammy) Status: New => In Progress ** Changed in: mstflint (Ubuntu Mantic) Status: New => In Progress ** Changed in: mstflint (Ubuntu Jammy) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: mstflint (Ubuntu Mantic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060026 Title: backport 4.26.0 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2060026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051571] Re: jammy: 4.21.0-7 dropped mstlink binary
** Changed in: mstflint (Ubuntu Jammy) Status: New => In Progress ** Changed in: mstflint (Ubuntu Jammy) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051571 Title: jammy: 4.21.0-7 dropped mstlink binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2051571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2043098] Re: mstflint-dkms FTBS with linux 6.5 on jammy
** Changed in: mstflint (Ubuntu Jammy) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2043098 Title: mstflint-dkms FTBS with linux 6.5 on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2043098/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059316] Re: backport arm64 THP improvements from 6.9
I've build-tested on all architectures in this PPA: https://launchpad.net/~dannf/+archive/ubuntu/mthp/+packages I manually tested on a few systems, timing a full kernel build w/ the Ubuntu config in a tmpfs (both to stress the system, and look for performance differences). - ppc64el / Power9 - no performance difference - x86 - AMD EPYC/Naples - 11% improvement - Ampere AltraMax (-generic) - 19% improvement ** Description changed: Initial support for multi-size THP landed upstream in v6.8. In the 6.9 merge window, 2 other series have landed that show significant performance improvements on arm64 mm/memory: optimize fork() with PTE-mapped THP - https://lkml.iu.edu/hypermail/linux/kernel/2401.3/02766.html + https://lkml.iu.edu/hypermail/linux/kernel/2401.3/02766.html Transparent Contiguous PTEs for User Mappings: - https://lwn.net/Articles/962330/ + https://lwn.net/Articles/962330/ On an Ampere AltraMax system w/ 4K page size, kernel builds in a tmpfs are reduced from 6m30s to 5m17s, a ~19% improvement. + + It has been reported that this can have a *10x* improvement for certain + GPU workloads on ARM: + + https://lwn.net/Articles/954094/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059316 Title: backport arm64 THP improvements from 6.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059316] Re: backport arm64 THP improvements from 6.9
** Changed in: linux (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059316 Title: backport arm64 THP improvements from 6.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059316] Re: backport arm64 THP improvements from 6.9
** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059316 Title: backport arm64 THP improvements from 6.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059316] [NEW] backport arm64 THP improvements from 6.9
Public bug reported: Initial support for multi-size THP landed upstream in v6.8. In the 6.9 merge window, 2 other series have landed that show significant performance improvements on arm64 mm/memory: optimize fork() with PTE-mapped THP https://lkml.iu.edu/hypermail/linux/kernel/2401.3/02766.html Transparent Contiguous PTEs for User Mappings: https://lwn.net/Articles/962330/ On an Ampere AltraMax system w/ 4K page size, kernel builds in a tmpfs are reduced from 6m30s to 5m17s, a ~19% improvement. ** Affects: 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/2059316 Title: backport arm64 THP improvements from 6.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055082] Re: IB peer memory feature regressed in 6.5
= Verification = $ cat /proc/version Linux version 6.5.0-27-generic (buildd@lcy02-amd64-059) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.41) #28-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 7 18:21:00 UTC 2024 ubuntu@ubuntu:~/autotest-client-tests/ubuntu_performance_gpudirect_rdma/nvidia-peermem-test$ ./nvidia-peermem-test.sh -m peermem Repository: 'Types: deb URIs: https://ppa.launchpadcontent.net/canonical-nvidia/perftest+cuda/ubuntu/ Suites: mantic Components: main ' Description: Used internal for kernel regression testing More info: https://launchpad.net/~canonical-nvidia/+archive/ubuntu/perftest+cuda Adding repository. Found existing deb entry in /etc/apt/sources.list.d/canonical-nvidia-ubuntu-perftest_cuda-mantic.sources Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease Hit:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu mantic-security InRelease Hit:4 http://archive.ubuntu.com/ubuntu mantic-backports InRelease Hit:5 http://archive.ubuntu.com/ubuntu mantic-proposed InRelease Hit:6 https://ppa.launchpadcontent.net/canonical-nvidia/perftest+cuda/ubuntu mantic InRelease Hit:7 https://ppa.launchpadcontent.net/dannf/dannf/ubuntu mantic InRelease Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done perftest is already the newest version (24.01.0+0.38-1+perftest+cuda.1~ubuntu23.10.1). 0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded. Reading package lists... Done Building dependency tree... Done Reading state information... Done opensm is already the newest version (3.3.23-2). 0 upgraded, 0 newly installed, 0 to remove and 10 not upgraded. --use_cuda= Use CUDA specific device for GPUDirect RDMA testing Perftest doesn't supports CUDA tests with inline messages: inline size set to 0 * Waiting for client to connect... * Perftest doesn't supports CUDA tests with inline messages: inline size set to 0 initializing CUDA initializing CUDA Listing all CUDA devices in system: CUDA device 0: PCIe address is 07:00 CUDA device 1: PCIe address is 0F:00 CUDA device 2: PCIe address is 47:00 CUDA device 3: PCIe address is 4E:00 CUDA device 4: PCIe address is 87:00 CUDA device 5: PCIe address is 90:00 CUDA device 6: PCIe address is B7:00 CUDA device 7: PCIe address is BD:00 Picking device No. 1 [pid = 15582, dev = 1] device name = [NVIDIA A100-SXM4-40GB] creating CUDA Ctx Listing all CUDA devices in system: CUDA device 0: PCIe address is 07:00 CUDA device 1: PCIe address is 0F:00 CUDA device 2: PCIe address is 47:00 CUDA device 3: PCIe address is 4E:00 CUDA device 4: PCIe address is 87:00 CUDA device 5: PCIe address is 90:00 CUDA device 6: PCIe address is B7:00 CUDA device 7: PCIe address is BD:00 Picking device No. 0 [pid = 15576, dev = 0] device name = [NVIDIA A100-SXM4-40GB] creating CUDA Ctx making it the current CUDA Ctx cuMemAlloc() of a 16777216 bytes GPU buffer allocated GPU buffer address at 7c014600 pointer=0x7c014600 --- RDMA_Write BW Test Dual-port : OFF Device : mlx5_6 Number of qps : 1Transport type : IB Connection type : RC Using SRQ : OFF PCIe relax order: ON making it the current CUDA Ctx cuMemAlloc() of a 16777216 bytes GPU buffer allocated GPU buffer address at 7a08b400 pointer=0x7a08b400 --- RDMA_Write BW Test Dual-port : OFF Device : mlx5_2 Number of qps : 1Transport type : IB Connection type : RC Using SRQ : OFF PCIe relax order: ON ibv_wr* API : ON TX depth: 128 CQ Moderation : 100 Mtu : 4096[B] Link type : IB Max inline data : 0[B] rdma_cm QPs : OFF Data ex. method : Ethernet --- ibv_wr* API : ON CQ Moderation : 100 Mtu : 4096[B] Link type : IB Max inline data : 0[B] rdma_cm QPs : OFF Data ex. method : Ethernet --- local address: LID 0x01 QPN 0x0029 PSN 0x6763b2 RKey 0x180eef VAddr 0x007a08b480 local address: LID 0x02 QPN 0x36ef PSN 0x149b7b RKey 0x180efd VAddr 0x007c014680 remote address: LID 0x02 QPN 0x36ef PSN 0x149b7b RKey 0x180efd VAddr 0x007c014680 --- #bytes #iterationsBW peak[MB/sec]BW average[MB/sec] MsgRate[Mpps] remote address: LID 0x01 QPN 0x0029 PSN 0x6763b2 RKey 0x180eef VAddr 0x007a08b480
[Bug 1804481] Re: SecureBoot support for arm64
** Changed in: shim-signed (Ubuntu Cosmic) Status: Triaged => Won't Fix ** Changed in: shim-signed (Ubuntu Bionic) Status: Triaged => Fix Released ** Changed in: linux-signed (Ubuntu Cosmic) Status: Triaged => Won't Fix ** Changed in: linux-meta (Ubuntu Cosmic) Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu Cosmic) Status: Triaged => Won't Fix ** Changed in: linux-signed (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: linux-meta (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: linux-signed-hwe-edge (Ubuntu) Status: New => Fix Released ** Changed in: linux-meta (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804481 Title: SecureBoot support for arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2051571] Re: jammy: 4.21.0-7 dropped mstlink binary
I've add mstflint-dkms to mstflint/noble: https://launchpad.net/ubuntu/+source/mstflint/4.26.0+1-2ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2051571 Title: jammy: 4.21.0-7 dropped mstlink binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/2051571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055082] [NEW] IB peer memory feature regressed in 6.5
Public bug reported: [Impact] The GPU Direct over Infiniband feature of NVIDIA GPUs no longer works on jammy/hwe kernels that have migrated to 6.5 *except* for the -nvidia kernel, which pulled in support via bug 2049537. We have carried this patch since 5.4 (see bug 1923104). We do not plan to carry this patch into 6.8 or later - we are working on a deprecation post for that to give users some time to migrate. [Test Case] https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/tree/ubuntu_performance_gpudirect_rdma ** Affects: linux (Ubuntu) Importance: Undecided Status: Won't Fix ** Affects: linux (Ubuntu Mantic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Won't Fix ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055082 Title: IB peer memory feature regressed in 6.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1976267] Re: edk2 ftbfs in jammy with -march=x86-64-v3
** Changed in: edk2 (Ubuntu) Status: Triaged => In Progress ** Changed in: edk2 (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1976267 Title: edk2 ftbfs in jammy with -march=x86-64-v3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1976267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
Yeah, I don't think an autopkgtest is a requirement. Having the test live within the package itself would make it more accessible, and autopkgtest was my first thought as to how to do that. But I don't see a "disable by default" flag, and I agree that huge downloads on every test run could be a problem. It would still be nice IMO if the test was integrated into the package though, even if it needs to run manually. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970672 Title: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973153] Re: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel", "howzit-kernel"
Patches are now queued for all applicable stable trees (linux-4.14.y+) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973153 Title: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel", "howzit-kernel" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1973153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970672] Re: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte."
Thanks everyone for trying to tackle this long-standing issue. fwiw, here's my $0.02 no how we could proceed: Someone should draft a special case page for makedumpfile: https://wiki.ubuntu.com/StableReleaseUpdates#Documentation_for_Special_Cases I'm happy to review/provide feedback, but I'd rather someone who would be carrying out the plan drive it. As others have mentioned, testing is the hard part, and we need to define what will be tested in the special case documentation. Since makedumpfile is really just a filter, I don't think we need to (or reasonably could) boot a bunch of systems in different configs and generate crashdumps for every new update. Rather, i think we could build a repository of representative, unfiltered, /proc/vmcore files that focal's existing makedumpfile can parse. Then we can just check that all of those files can still be parsed by the proposed makedumpfile. With some scripting and a multi-architecture cloud, this could be automated. In fact, if this vmcore repo were online, we could implement this an autopkgtest (w/ needs-internet set). But we should also do at least one end-to-end kdump, just to make sure the kdump-tools->makedumpfile interface hasn't been broken. What is a representative sample? One of each of the current LTS and HWE kernels on amd64, arm64, ppc64el and s390x seems like an obvious start (or the subset of those that actually work today). I don't think the machine type is as important, VMs should be fine IMO. If we know of examples where different machines expose structures differently in a way that makedumpfile cares about, then perhaps add those as well. Once a new makedumpfile lands that adds support for a new HWE kernel, we should probably then update the repo w/ vmcore samples from that kernel, so we can make sure the next update doesn't regress that support (probably convenient to do when verifying the SRU, since I imagine we'd be testing that it works w/ the new HWE kernel then anyway). It'd be good to note in the special case request that kdump-tools does fall back to a raw /proc/vmcore file cp if makedumpfile fails, which can mitigate regressions for a subset of users - those with the necessary disk space and lack of time constraints. While I agree that crash falls into the same category, I don't think it necessarily needs to happen at the same time. Obviously users running focal need to dump their vmcore using focal - bug for developers debugging a crash, I don't think it is to onerous to use a newer version of Ubuntu. Again, I'm no saying we *shouldn't* add crash to the special case, it just seems like a makedumpfile exception is significantly more important. Finally, I don't think we need to commit to a frequency of backports, or a point at which they will stop. Rather we can just stick to agreeing on how it *can* be done when someone has the time/interest in doing it. Guillherme's LTS->LTS+1 scheme sounds like a reasonable pattern to shoot for, but if that doesn't happen every time, we're still improving the situation over the status quo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970672 Title: makedumpfile falls back to cp with "__vtop4_x86_64: Can't get a valid pmd_pte." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1970672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973153] Re: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel", "howzit-kernel"
A fix for this is currently queued in linux-next: commit 1bbc21785b7336619fb6a67f1fff5afdaf229acc Author: Lorenzo Pieralisi Date: Thu Apr 7 11:51:20 2022 +0100 ACPI: sysfs: Fix BERT error region memory mapping My plan is to propose this for stable after it lands during the merge window. ** Changed in: ubuntu-kernel-tests Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973153 Title: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel", "howzit-kernel" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1973153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973153] Re: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel", "howzit-kernel"
** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973153 Title: kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17 ARM64 "helo-kernel", "howzit-kernel" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1973153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
= bionic verification = ubuntu@d06-4:~$ cat /proc/version Linux version 4.15.0-179-generic (buildd@bos02-arm64-025) (gcc version 7.5.0 (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04)) #188-Ubuntu SMP Tue May 10 20:51:17 UTC 2022 ubuntu@d06-4:~$ grep domain2 /proc/schedstat | wc -l 128 ubuntu@d06-4:~$ grep domain3 /proc/schedstat | wc -l 128 ubuntu@d06-4:~$ ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1951289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
@kernel when we've already tested a kernel in its GA release, do we also now need to retest the HWE backport? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
** Description changed: [Impact] The LTP cpuset_sched_domains test, authored by Miao Xie, fails on a Kunpeng920 server that has 4 NUMA nodes: - https://launchpad.net/bugs/1951289 + https://launchpad.net/bugs/1951289 This does appear to be a real bug. /proc/schedstat displays 4 domain levels for CPUs on 2 of the nodes, but only 3 levels for the others 2 (see below). I assume this means the scheduler is making suboptimal decisions about where to place/move processes. [Test Case] On a 128 core Kunpeng 920 system, observe that half the CPUs are missing a 3rd level scheduling domain: ubuntu@d06-4:~$ grep domain2 /proc/schedstat | wc -l 128 ubuntu@d06-4:~$ grep domain3 /proc/schedstat | wc -l 64 - ubuntu@d06-4:~$ + ubuntu@d06-4:~$ [What Could Go Wrong] - This changes the code used for populating sched domains, so it could potentially break on other systems, potentially leading to poor scheduling characteristics (higher latencies, lower overall throughput etc). + This changes the code used for populating sched domains, so it could potentially break on other systems, leading to poor scheduling characteristics (higher latencies, lower overall throughput etc). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1951289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960207] Re: Ubuntu 20.04 LTS: Apply critical git diffs from version 18
It's not a question of if it *could* be backported - it's a question of whether or not we can demonstrate that such a backport has a negligible risk of regression to existing 20.04 users. See https://wiki.ubuntu.com/StableReleaseUpdates for details. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960207 Title: Ubuntu 20.04 LTS: Apply critical git diffs from version 18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1960207/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956086] Re: config CONFIG_HISI_PMU for kunpeng920
** Description changed: [Impact] - We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. + We have Hisilicon PMU modules built-in and they can not be unloaded. There is no way to replace with a updated module unless we build it as module. It also wastes memory on arm64 systems based on other SoCs. [Test Plan] `lsmod | grep hisi_uncore` shall see 4 modules loaded and they can be unloaded. [Regression Risk] CONFIG_HISI_PMU shall be only affected Hisilicon platforms that HISI0213 is found in ACPI tables. We shall have perf test run on these platforms and others have lowest risk. = [Bug Description] hisi pmu support x.ko module to use it for kunpeng920 [Steps to Reproduce] 1) cd /lib/modules/$(uname -r)/kernel/drivers/perf/hisilicon 2) check *.ko 3) [Actual Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=y [Expected Results] @ubuntu:~$ cat /boot/config-4.15.0-140-generic | grep -i CONFIG_HISI_PMU CONFIG_HISI_PMU=m [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] drivers/perf: hisi: Permit modular builds of HiSilicon uncore drivers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956086 Title: config CONFIG_HISI_PMU for kunpeng920 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1956086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
** Description changed: - On scobee-kernel(arm64) with hirsute:linux(5.11.0-41.45) for - sru-20211108 there are several reports about the sched domain not - covering the full range. The same does not happen on kuzzle. But 32 is a - bit of a suspicious number. + [Impact] + The LTP cpuset_sched_domains test, authored by Miao Xie, fails on a Kunpeng920 + server that has 4 NUMA nodes: + https://launchpad.net/bugs/1951289 - Running tests... - cpuset_sched_domains 1 TINFO: CPUs are numbered continuously starting at 0 (0-127) - cpuset_sched_domains 1 TINFO: Nodes are numbered continuously starting at 0 (0-3) - cpuset_sched_domains 1 TINFO: root group load balance test - cpuset_sched_domains 1 TINFO: sched load balance: 0 - cpuset_sched_domains 1 TINFO: CPU hotplug: - cpuset_check_domains1 TPASS : check_sched_domains passed - cpuset_sched_domains 1 TPASS: partition sched domains succeeded. - cpuset_sched_domains 3 TINFO: root group load balance test - cpuset_sched_domains 3 TINFO: sched load balance: 1 - cpuset_sched_domains 3 TINFO: CPU hotplug: - cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). - cpuset_sched_domains 3 TFAIL: partition sched domains failed. - cpuset_sched_domains 5 TINFO: root group load balance test - cpuset_sched_domains 5 TINFO: sched load balance: 0 - cpuset_sched_domains 5 TINFO: CPU hotplug: - cpuset_check_domains1 TPASS : check_sched_domains passed - cpuset_sched_domains 5 TPASS: partition sched domains succeeded. - cpuset_sched_domains 7 TINFO: root group load balance test - cpuset_sched_domains 7 TINFO: sched load balance: 0 - cpuset_sched_domains 7 TINFO: CPU hotplug: - cpuset_check_domains1 TPASS : check_sched_domains passed - cpuset_sched_domains 7 TPASS: partition sched domains succeeded. - cpuset_sched_domains 9 TINFO: root group load balance test - cpuset_sched_domains 9 TINFO: sched load balance: 1 - cpuset_sched_domains 9 TINFO: CPU hotplug: - cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). - cpuset_sched_domains 9 TFAIL: partition sched domains failed. - cpuset_sched_domains 11 TINFO: root group load balance test - cpuset_sched_domains 11 TINFO: sched load balance: 1 - cpuset_sched_domains 11 TINFO: CPU hotplug: - cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). - cpuset_sched_domains 11 TFAIL: partition sched domains failed. - cpuset_sched_domains 13 TINFO: general group load balance test - cpuset_sched_domains 13 TINFO: root group info: - cpuset_sched_domains 13 TINFO: sched load balance: 0 - cpuset_sched_domains 13 TINFO: general group info: - cpuset_sched_domains 13 TINFO: cpus: - - cpuset_sched_domains 13 TINFO: sched load balance: 1 - cpuset_check_domains1 TPASS : check_sched_domains passed - cpuset_sched_domains 13 TPASS: partition sched domains succeeded. - cpuset_sched_domains 15 TINFO: general group load balance test - cpuset_sched_domains 15 TINFO: root group info: - cpuset_sched_domains 15 TINFO: sched load balance: 0 - cpuset_sched_domains 15 TINFO: general group info: - cpuset_sched_domains 15 TINFO: cpus: 1 - cpuset_sched_domains 15 TINFO: sched load balance: 0 - cpuset_check_domains1 TPASS : check_sched_domains passed - cpuset_sched_domains 15 TPASS: partition sched domains succeeded. - cpuset_sched_domains 17 TINFO: general group load balance test - cpuset_sched_domains 17 TINFO: root group info: - cpuset_sched_domains 17 TINFO: sched load balance: 1 - cpuset_sched_domains 17 TINFO: general group info: - cpuset_sched_domains 17 TINFO: cpus: - - cpuset_sched_domains 17 TINFO: sched load balance: 1 - cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). - cpuset_sched_domains 17 TFAIL: partition sched domains failed. - cpuset_sched_domains 19 TINFO: general group load balance test - cpuset_sched_domains 19 TINFO: root group info: - cpuset_sched_domains 19 TINFO: sched load balance: 1 - cpuset_sched_domains 19 TINFO: general group info: - cpuset_sched_domains 19 TINFO: cpus: 1 - cpuset_sched_domains 19 TINFO: sched load balance: 1 - cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). - cpuset_sched_domains 19 TFAIL: partition sched domains failed. - cpuset_sched_domains 21 TINFO: general group load balance test - cpuset_sched_domains 21 TINFO: root group info: - cpuset_sched_domains 21 TINFO: sched load balance: 0 -
[Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1951289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
5.4.183 has now been merged into focal ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1951289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967754] Re: ubuntu 22.04 jammy, mlx5, can't change flow steering mode
We decided the best approach was to revert the break patch which is now done in 5.15.y upstream: commit f1607e13ed715f3b6433361f8ea5d4aa79f03b94 Author: dann frazier Date: Thu Apr 7 14:16:42 2022 -0600 Revert "net/mlx5: Accept devlink user input after driver initialization complete" Which was released in v5.15.34, and is being tracked for jammy inclusion in bug 1969107. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967754 Title: ubuntu 22.04 jammy, mlx5, can't change flow steering mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1946773] Re: "An error occurred. Press enter to start a shell"
On Wed, Apr 27, 2022 at 2:25 PM Jeff Lane <1946...@bugs.launchpad.net> wrote: > Given that, I'm now curious about how this was set up on the Ampere > server too, and if anyone tried what I did by putting Desktop on a local > machine and mounting the ISO from there, rather than from a remote > location outside the DC. > > I suspect you were doing this from home as well (am I right?) and even > with your uplink which has to be better than mine, the latency is still > too great. Yeah, I'm pretty sure I was using a browser on my laptop to feed media to a server in the data center over a VPN. When I'm testing I typically prioritize ease of setup over deployment time, because I can just let the install go in the background and do other things while it runs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946773 Title: "An error occurred. Press enter to start a shell" To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1946773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951032] Re: AArch64: Backport memcpy improvements
2.31-0ubuntu9.7 vs 2.31-0ubuntu9.9 = X-Gene = length | before (MiB/s) | after (MiB/s) |delta --|||-- 32768 | 122.27 | 122.26 | -0.00% 65536 | 216.55 | 215.81 | -0.34% 131072 | 321.97 | 322.25 |0.09% 262144 | 515.08 | 515.29 |0.04% 524288 | 934.42 | 934.58 |0.02% 1048576 |1781.58 |1783.57 |0.11% = ThunderX = length | before (MiB/s) | after (MiB/s) |delta --|||-- 32768 | 56.52 | 56.57 |0.09% 65536 | 86.45 | 86.54 |0.10% 131072 | 131.51 | 131.58 |0.06% 262144 | 235.38 | 235.50 |0.05% 524288 | 428.95 | 429.21 |0.06% 1048576 | 578.01 | 578.32 |0.05% = ThunderX2 = length | before (MiB/s) | after (MiB/s) |delta --|||-- 32768 | 124.61 | 121.43 | -2.54% 65536 | 267.12 | 267.78 |0.25% 131072 | 508.33 | 509.59 |0.25% 262144 | 976.22 | 986.22 |1.02% 524288 |1876.75 |1894.43 |0.94% 1048576 |3723.27 |3747.04 |0.64% = Hi1616 = length | before (MiB/s) | after (MiB/s) |delta --|||-- 32768 | 135.41 | 132.37 | -2.25% 65536 | 251.27 | 248.20 | -1.22% 131072 | 473.71 | 471.16 | -0.54% 262144 | 938.66 | 934.16 | -0.48% 524288 |1627.75 |1611.05 | -1.03% 1048576 |2919.80 |2912.29 | -0.26% = Hi1620 = length | before (MiB/s) | after (MiB/s) |delta --|||-- 32768 | 213.00 | 213.93 |0.44% 65536 | 407.69 | 408.29 |0.15% 131072 | 755.45 | 761.75 |0.83% 262144 |1409.21 |1418.65 |0.67% 524288 |2364.40 |2388.89 |1.04% 1048576 |4024.87 |4080.98 |1.39% = Altra = length | before (MiB/s) | after (MiB/s) |delta --|||-- 32768 | 268.34 | 285.36 |6.34% 65536 | 519.58 | 549.29 |5.72% 131072 | 999.22 |1049.03 |4.98% 262144 |1853.42 |1942.76 |4.82% 524288 |2654.58 |2650.23 | -0.16% 1048576 |4030.24 |3955.51 | -1.85% -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951032 Title: AArch64: Backport memcpy improvements To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1951032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
Released upstream in 5.4.183. The inclusion of the changes from that stable release is being tracked in bug 1969239. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1951289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946773] Re: "An error occurred. Press enter to start a shell"
> Point is, I don't think the issue you're seeing is actually related to this bug at this point. The error appears to be the same in the screenshot @zhouling12 provided - so it seems like we are still seeing this issue w/ high-latency media. Or do you have reason to believe the cause is different than what I reported here? Having lower latency media does seem like a valid workaround but, IMO, high-latency media is a significant enough use case that we should try and support it. I don't know that we can expect users to all have systems "next door" to their install targets to use for media hosting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946773 Title: "An error occurred. Press enter to start a shell" To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1946773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946773] Re: "An error occurred. Press enter to start a shell"
I wonder if there is some scope creep in this bug. The bug I filed has this symptom: - Ubuntu 21.10 ubuntu-server ttyAMA0 connecting... waiting for cloud-init... An error occurred. Press enter to start a shell - And that should be fix committed if I understand comment #13 correctly (possibly commit 05f3db94a?). Is this the symptom you are seeing @zhouling12, meaning the fix maybe incomplete, or are you seeing some other issue also correlated w/ slow/BMC-emulated media? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946773 Title: "An error occurred. Press enter to start a shell" To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1946773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954833] Re: net: ethernet: microchip: lan743x: Increase rx ring size to improve rx performance
Due to lack of hardware, we are unable to verify a backport of this fix,
so I'll go ahead and mark this bug "Won't Fix". If you are impacted by
this and are able to perform the necessary performance testing to verify
a backport, please reopen and we can move forward.
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Jammy)
Assignee: dann frazier (dannf) => (unassigned)
** Changed in: linux (Ubuntu Impish)
Assignee: dann frazier (dannf) => (unassigned)
** Changed in: linux (Ubuntu Hirsute)
Assignee: dann frazier (dannf) => (unassigned)
** Changed in: linux (Ubuntu Focal)
Assignee: dann frazier (dannf) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954833
Title:
net: ethernet: microchip: lan743x: Increase rx ring size to improve rx
performance
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954833/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952933] Re: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952933 Title: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967754] Re: ubuntu 22.04 jammy, mlx5, can't change flow steering mode
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967754 Title: ubuntu 22.04 jammy, mlx5, can't change flow steering mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
reported upstream: https://lists.gnu.org/archive/html/grub- devel/2022-04/msg00055.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
** Merge proposal linked: https://code.launchpad.net/~xypron/grub/+git/grub/+merge/419407 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
Well spotted Heinrich. I'd hypothesized that something was shutting down
the network stack, but didn't yet no where to look, and overlooked
grub_net_fini_hw() message! With that hint, I went ahead and tried
commenting out[*] the registration of that callback, and voila, the
ReadFile2 initramfs loading from TFTP worked:
loader/efi/linux.c:348: Providing initrd via LOAD_FILE2_PROTOCOL
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Exiting boot services...
But I'm not sure of the correct way to address it. Perhaps the kernel's
efi stub needs to own network device shutdown to do this properly? I'm
happy to bring this discussion up on the mailing list. But, for jammy,
seems like disabling ReadFile2 initramfs for !riscv64 would be the
safest approach at this point.
[*]
Index: grub2-unsigned-2.06/grub-core/net/net.c
===
--- grub2-unsigned-2.06.orig/grub-core/net/net.c
+++ grub2-unsigned-2.06/grub-core/net/net.c
@@ -1818,11 +1818,11 @@ grub_net_fini_hw (int noreturn __attribu
return GRUB_ERR_NONE;
}
-static grub_err_t
+/*static grub_err_t
grub_net_restore_hw (void)
{
return GRUB_ERR_NONE;
-}
+ }*/
static int
grub_config_search_through (char *config, char *suffix,
@@ -2048,9 +2048,9 @@ GRUB_MOD_INIT(net)
grub_dns_init ();
grub_net_open = grub_net_open_real;
- fini_hnd = grub_loader_register_preboot_hook (grub_net_fini_hw,
+ /* fini_hnd = grub_loader_register_preboot_hook (grub_net_fini_hw,
grub_net_restore_hw,
-
GRUB_LOADER_PREBOOT_HOOK_PRIO_DISK);
+
GRUB_LOADER_PREBOOT_HOOK_PRIO_DISK);*/
grub_net_poll_cards_idle = grub_net_poll_cards_idle_real;
#ifdef GRUB_MACHINE_EFI
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967562
Title:
jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1967562/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
Any objection to dropping flash-kernel from ARM cloud images starting w/ jammy+1? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918427 Title: curtin: install flash-kernel in arm64 UEFI unexpected To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1918427/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
Thanks Amir. If the test results are the same w/ and w/o these patches, then I assume those tests are regression tests. Are you able to also confirm that the new functionality (CX7 software steering support) is working as expected? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
I randomly picked another ARM server, a Cavium ThunderX system, and it also fails to net boot w/ jammy's GRUB, but works fine w/ the patch in comment #16. So this is looking like possibly an architecture-wide issue. I tested on an x86 VM, but I didn't see any of the LoadFile2 messages. I assume (didn't check the code) that LoadFile2 initramfs is disabled there. ** Changed in: grub2-unsigned (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: dann frazier (dannf) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
Removing efi-implement-grub_efi_run_image.patch didn't avoid the problem, nor did removing both that and efi-implemented- LoadFile2-initrd-loading-protocol-fo.patch, but that appears to just be because the arm64 code gets migrated to the efi loader code later in the series, basically reintroducing the LoadFile2 support. Instead, I just made the following change, which does avoid the problem: Index: grub2-unsigned-2.06/grub-core/loader/efi/linux.c === --- grub2-unsigned-2.06.orig/grub-core/loader/efi/linux.c +++ grub2-unsigned-2.06/grub-core/loader/efi/linux.c @@ -88,7 +88,7 @@ grub_arch_efi_linux_check_image (struct * LoadFile2 based initrd loading protocol if the image version is >= 1. */ if (optional_header->major_image_version >= 1) -initrd_use_loadfile2 = 1; +initrd_use_loadfile2 = 0; else initrd_use_loadfile2 = 0; -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
I turned on grub debugging (set debug=all in grub.cfg), and this seems interesting. The "error: couldn't send network packet." message may actually be telling us something is wrong with downloading the initrd. Full log attached, here's a filtered version: [...] loader/efi/linux.c:80: UEFI stub kernel: loader/efi/linux.c:81: PE/COFF header @ 0040 loader/efi/linux.c:95: LoadFile2 initrd loading enabled loader/efi/linux.c:459: kernel file size: 46496128 loader/efi/linux.c:461: kernel numpages: 11352 loader/efi/linux.c:478: kernel @ 0xa1e43000 kern/disk.c:196: Opening `tftp,10.229.58.59'... disk/efi/efidisk.c:482: opening tftp kern/disk.c:281: Opening `tftp,10.229.58.59' failed. kern/disk.c:295: Closing `tftp'. kern/verifiers.c:88: file: /casper/initrd type: 131076 loader/efi/linux.c:396: LoadFile2 initrd loading protocol installed ] loader/efi/linux.c:141: Installed/updated FDT configuration table @ 0x0 loader/efi/linux.c:191: linux command line: 'BOOT_IMAGE=/casper/vmlinuz root=/dev/ram0 ramdisk_size=150 ip=dhcp url=http://cdimage.ubuntu.com/ubuntu-server/daily-live/20220408/jammy-live-serv er-arm64.iso --- debug' kern/efi/sb.c:111: UEFI Secure Boot state: Disabled loader/efi/peimage.c:215: PE-COFF header checked loader/efi/peimage.c:282: sections loaded loader/efi/peimage.c:493: no relocations loader/efi/peimage.c:709: Executing image loaded at 0x9f0b Entry point 0xa0fb8428 Size 0x02d9 EFI stub: Booting Linux Kernel... EFI stub: Generating empty DTB loader/efi/linux.c:348: Providing initrd via LOAD_FILE2_PROTOCOL net/net.c:1596: error receiving: 28: couldn't send network packet net/net.c:1596: error receiving: 28: couldn't send network packet net/net.c:1596: error receiving: 28: couldn't send network packet net/net.c:1596: error receiving: 28: couldn't send network packet net/net.c:1596: error receiving: 28: couldn't send network packet net/net.c:1596: error receiving: 28: couldn't send network packet net/net.c:1596: error receiving: 28: couldn't send network packet net/net.c:1596: error receiving: 28: couldn't send network packet error: couldn't send network packet. EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Exiting boot services... ** Attachment added: "grub-debug.log" https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1967562/+attachment/5578350/+files/grub-debug.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
GRUB is responsible for loading the initrd into memory, so it is possible that this is a GRUB regression. Also, this message is new to me: EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path So maybe this is related to a new GRUB initrd loading method? To test that, I grabbed focal's grubnetaa64.efi[*] and retested. This actually worked, and contains no "LINUX_EFI_INITRD_MEDIA_GUID" messages in the stub: EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... [0.00] Booting Linux on physical CPU 0x12 [0x413fd0c1] So, adding a grub task. [*] http://ports.ubuntu.com/ubuntu-ports/dists/focal/main/uefi/grub2-arm64/2.04-1ubuntu26/grubnetaa64.efi.signed ** Attachment added: "howzit-iso-console+focal-grub.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+attachment/5578349/+files/howzit-iso-console+focal-grub.log ** Also affects: grub2-unsigned (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/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
The iso-booted-kernel has no problem unpacking the initramfs: [ 15.282839] Trying to unpack rootfs image as initramfs... [...] [ 15.935483] Freeing initrd memory: 103248K But that's interesting, the freed initrd memory size reported is different here. When PXE-booted, it was 103244K. 103248K actually matches the initrd size reported by `ls`. I assumed some kind of rounding error, but maybe that 4K difference is a clue. EDIT: No, turns out I was pointing at a daily ISO build and it has been updated, and initrd sizes between the two have a 4K initrd difference. ** Attachment added: "howzit-iso-console.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+attachment/5578348/+files/howzit-iso-console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967562] Re: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
I can reproduce, and I've attached the full console log (!quiet, +debug). Here's some interesting pieces of the log: EFI stub: Booting Linux Kernel... EFI stub: Generating empty DTB error: couldn't send network packet. EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Exiting boot services... [0.00] Booting Linux on physical CPU 0x12 [0x413fd0c1] [0.00] Linux version 5.15.0-25-generic (buildd@bos02-arm64-058) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #25-Ubuntu SMP Wed Mar 30 15:57:31 UTC 2022 (Ubuntu 5.15.0-25.25-generic 5.15.30) [...] [ 15.338070] Trying to unpack rootfs image as initramfs... [ 15.439137] Initramfs unpacking failed: invalid magic at start of compressed archive [ 15.461425] Freeing initrd memory: 103244K [...] We can see at the end there that the initrd failed to unpack, and that will definitely lead to a "Unable to mount root fs" panic. But why did it fail to unpack? One possibility is that the initrd failed to download. The TFTP server does report that it downloaded: Apr 8 19:38:59 avoton02 in.tftpd[4218]: RRQ from 10.229.58.47 filename /casper/vmlinuz Apr 8 19:39:02 avoton02 in.tftpd[4220]: RRQ from 10.229.58.47 filename /casper/vmlinuz Apr 8 19:39:06 avoton02 in.tftpd[4221]: RRQ from 10.229.58.47 filename /casper/initrd OK, then maybe it only partially downloaded? Well, the amount of memory the kernel reports freeing is close to the size of the initrd, so that's probably not it: $ du -s /srv/tftp/casper/initrd 103248 /srv/tftp/casper/initrd Then perhaps the kernel doesn't support decompressing this compression format. What is the compression format? $ file /srv/tftp/casper/initrd /srv/tftp/casper/initrd: Zstandard compressed data (v0.8+), Dictionary ID: None Does the kernel support that? Let's look at the kernel config: ubuntu@avoton02:/tmp$ dpkg-deb -x linux-modules-5.15.0-25-generic_5.15.0-25.25_arm64.deb x ubuntu@avoton02:/tmp$ grep ZSTD_DECOMPRESS x/boot/config-5.15.0-25-generic CONFIG_ZSTD_DECOMPRESS=y hm.. it does. That's weird. The other mystery is that this all seems to work when booted from the ISO. Let's take a look at that boot log and see if we can spot anything different. ** Attachment added: "howzit-pxe-console.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+attachment/5578333/+files/howzit-pxe-console.log ** Changed in: subiquity (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952933] Re: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq
Now fixed in upstream release v5.15.33. ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952933 Title: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946773] Re: "An error occurred. Press enter to start a shell"
Just tested w/ a jammy image, and yeah - toram works, though it looks like it took about 50 minutes from boot to load the ISO over this interface. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946773 Title: "An error occurred. Press enter to start a shell" To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1946773/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
I've now updated the PPA w/ a kernel that reverts the patch that caused bug 1967754. Same package name, just version 5.15.0-25.25.25+lp1966194.2 now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952933] Re: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq
Upstream has gone ahead and reverted the problematic patches, and they are flowing into the various stable trees. ** Changed in: linux (Ubuntu Impish) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952933 Title: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952933/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966194] Re: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering
I've refreshed the above ppa to include the guys for bug 1967754, can you verify this build? sudo apt-add-repository ppa:dannf/lp1966194 sudo apt install linux-modules-extra-5.15.0-25.25-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966194 Title: [Jammy, mlx5, ConnectX-7] add CX7 support for software steering To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967754] Re: ubuntu 22.04 jammy, mlx5, can't change flow steering mode
@Amir: if that fixes the problem for you, would you mind submitting it to sta...@vger.kernel.org? I've verified that stable 5.15.y is impacted, which is where Ubuntu inherited it from. I also tested upstream 5.15.y w/ cf530217408e applied, and it does seem to fix this issue. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967754 Title: ubuntu 22.04 jammy, mlx5, can't change flow steering mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967562] Re: jammy beta (220330) arm iso kernel panic during pxe boot
** Changed in: subiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967562 Title: jammy beta (220330) arm iso kernel panic during pxe boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
