[Bug 2060437] Re: The module ib_ipoib does not load automatically on ubuntu server 24.04
** Changed in: linux (Ubuntu) Status: Incomplete => New ** Changed in: linux (Ubuntu Noble) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060437 Title: The module ib_ipoib does not load automatically on ubuntu server 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060437] Re: The module ib_ipoib does not load automatically on ubuntu server 24.04
I suspect it's not necessarily related to the card model, but just in case that is relevant, could you provide the model of the mellanox card you're using? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060437 Title: The module ib_ipoib does not load automatically on ubuntu server 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061373] Re: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta
Is this still happening with the latest images? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061373 Title: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2061373/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060924] Re: [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)"
** Also affects: subiquity (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/2060924 Title: [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059898] Re: ubuntu-24.04 daily build install failed with netwok cable connected
Can you confirm, the issue is summarized as thus: 1: NO network cable connected, installation is successful 2: Network cable connected and internet is available, installation is successful 3: Network cable connected, network is available, INTERNET is unavailable (airgapped lab), installation fails I believe from what you described elsewhere #3 is the case you are seeing, because you are in a lab with no external access, is that correct? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059898 Title: ubuntu-24.04 daily build install failed with netwok cable connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2059898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.
Something in a recent dnsmasq update broke KVM. I hit the same and found a workaround that gets me rolling again wtih KVM guests at least here's a quick shell summary: bladernr@galactica:~$ sudo virsh net-start default error: Failed to start network default error: internal error: Child process (VIR_BRIDGE_NAME=virbr0 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper) unexpected exit status 2: dnsmasq: failed to create listening socket for 192.168.123.1: Address already in use bladernr@galactica:~$ sudo virsh net-list Name State Autostart Persistent bladernr@galactica:~$ sudo apt-cache policy dnsmasq-base dnsmasq-base: Installed: 2.90-0ubuntu0.23.10.1 Candidate: 2.90-0ubuntu0.23.10.1 Version table: *** 2.90-0ubuntu0.23.10.1 500 500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu mantic-security/main amd64 Packages 100 /var/lib/dpkg/status 2.89-1 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages bladernr@galactica:~$ sudo apt install dnsmasq-base=2.89-1 bladernr@galactica:~$ sudo virsh net-start default Network default started bladernr@galactica:~$ sudo virsh net-list Name StateAutostart Persistent default active yes yes as you can see, as a workaround, reverting to the original Mantic version allows the NAT network to start and I can once again launch KVM guests on my machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055776 Title: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2055776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055776 Title: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2055776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
distroseries=lunar; sourcepackage=lxd; > component=None; status=Invalid; importance=Undecided; assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=lunar; > sourcepackage=qemu; component=main; status=Invalid; importance=Undecided; > assignee=sergio.duri...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=mantic; > sourcepackage=lxd; component=None; status=New; importance=Undecided; > assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=mantic; > sourcepackage=qemu; component=main; status=Confirmed; importance=Critical; > assignee=sergio.duri...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=noble; sourcepackage=lxd; > component=None; status=New; importance=Undecided; assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=noble; > sourcepackage=qemu; component=main; status=Confirmed; importance=Critical; > assignee=sergio.duri...@canonical.com; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: anilchabba bladernr goujm1 junggyumkim mcoskey > mjt+launchpad-tls paelzer racb rodsmith sergiodj > Launchpad-Bug-Reporter: Jeff Lane (bladernr) > Launchpad-Bug-Modifier: Sergio Durigan Junior (sergiodj) > Launchpad-Message-Rationale: Subscriber > Launchpad-Message-For: bladernr > > -- Jeff Lane Engineering Manager IHV/OEM Alliances and Server Certification "Entropy isn't what it used to be." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2012763] Re: qemu-system-amd64 max cpus is too low for latest processors
Hi Sergio, is there anything we can help with testing here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2012763 Title: qemu-system-amd64 max cpus is too low for latest processors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772434] Re: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches)
Closing, this is an old bug and this support likely landed long ago. ** Changed in: dellserver Status: In Progress => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772434 Title: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches) To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1772434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057745] Re: Failed to query node's BMC - >
** Package changed: checkbox (Ubuntu) => maas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057745 Title: Failed to query node's BMC - > To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/2057745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-screensaver (Ubuntu Quantal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to a duplicate bug report (1124282). https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-screensaver (Ubuntu Wily) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to a duplicate bug report (338057). https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-shell (Ubuntu Quantal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to a duplicate bug report (1124282). https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: gnome-shell (Ubuntu Wily) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to a duplicate bug report (371388). https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Changed in: unity (Ubuntu Wily) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to a duplicate bug report (338057). https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 49579] Re: screen doesn't lock when some menu is open
Release EOL ** Also affects: gnome-screensaver (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Quantal) Importance: Undecided Status: New ** Also affects: gnome-screensaver (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: unity (Ubuntu Wily) Importance: Undecided Status: New ** Changed in: unity (Ubuntu Quantal) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to a duplicate bug report (338057). https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972149] Re: "mcelog --client" cannot ouput after performing PFA test on Ubunt22.04 and SR850v2
** Changed in: mcelog (Ubuntu) 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/1972149 Title: "mcelog --client" cannot ouput after performing PFA test on Ubunt22.04 and SR850v2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mcelog/+bug/1972149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965241] Re: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events
** Tags added: servcert-359 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965241 Title: Ubuntu 22.04 and 20.04 DPC Fixes for Failure Cases of DownPort Containment events To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1965241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Hi Sujith - Can you update this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971151] Re: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
** Changed in: linux (Ubuntu) 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/1971151 Title: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883312] Re: [SRU] NVMe FC Auto-connect is not working for Ubuntu 20.04
If we get a customer with issues with this on Focal, we can revisit this, but now that 22.04 is out with a version of nvme-cli that is not affected, this is less likely to get sponsored otherwise. ** Changed in: nvme-cli (Ubuntu Focal) Status: New => Invalid ** Changed in: nvme-cli (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/1883312 Title: [SRU] NVMe FC Auto-connect is not working for Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1883312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971193] Re: Server Crash while running IO and switch port bounce test with 2K login session
Thanks @mfo! That is correct, the crash was seen there, but they determined it was generic and are pushing this to all the Linux OSVs. Also of note, that patch set is a general driver update and not all of those are relevant to this bug, I've asked them to pinpoint the patches that resolve this issue specifically with the intent of just pulling those. ** Description changed: + [Impact] Server crash and Call trace reported on one of the servers running IO and switch port bounce test from the 2K login session configuration. - Call Trace: [56048.470488] Call Trace: [56048.470489] _raw_spin_lock_irqsave+0x32/0x40 [56048.470489] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470490] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470490] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470490] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470491] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470491] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470492] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470492] ? __schedule+0x280/0x700 [56048.470492] ? finish_wait+0x80/0x80 [56048.470493] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470493] kthread+0x112/0x130 [56048.470493] ? kthread_flush_work_fn+0x10/0x10 [56048.470494] ret_from_fork+0x1f/0x40 [56048.470494] Kernel panic - not syncing: Hard LOCKUP - [56048.470495] CPU: 0 PID: 682 Comm: lpfc_worker_0 Kdump: loaded Tainted: G - IOE- - - 4.18.0-240.el8.x86_64 #1 + [56048.470495] CPU: 0 PID: 682 Comm: lpfc_worker_0 Kdump: loaded Tainted: G + IOE- - - 4.18.0-240.el8.x86_64 #1 [56048.470496] Hardware name: Dell Inc. PowerEdge R740/0DY2X0, BIOS 2.11.2 004/21/2021 [56048.470496] Call Trace: [56048.470496] [56048.470496] dump_stack+0x5c/0x80 [56048.470497] panic+0xe7/0x2a9 [56048.470497] ? __switch_to_asm+0x51/0x70 [56048.470497] nmi_panic.cold.9+0xc/0xc [56048.470498] watchdog_overflow_callback.cold.7+0x5c/0x70 [56048.470498] __perf_event_overflow+0x52/0xf0 [56048.470499] handle_pmi_common+0x1db/0x270 [56048.470499] ? __set_pte_vaddr+0x32/0x50 [56048.470499] ? __native_set_fixmap+0x24/0x30 [56048.470500] ? ghes_copy_tofrom_phys+0xd3/0x1c0 [56048.470500] ? __ghes_peek_estatus.isra.12+0x49/0xa0 [56048.470500] intel_pmu_handle_irq+0xbf/0x160 [56048.470501] perf_event_nmi_handler+0x2d/0x50 [56048.470501] nmi_handle+0x63/0x110 [56048.470501] default_do_nmi+0x4e/0x100 [56048.470502] do_nmi+0x128/0x190 [56048.470502] end_repeat_nmi+0x16/0x6a [56048.470503] RIP: 0010:native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470504] Code: 0f ba 2f 08 0f 92 c0 0f b6 c0 c1 e0 08 89 c2 8b 07 30 e4 09 d0 a9 00 01 ff ff 75 47 85 c0 74 0e 8b 07 84 c0 74 08 f3 90 8b 07 <84> c0 75 f8 b8 01 00 00 00 66 89 07 c3 8b 37 81 fe 00 01 00 00 75 [56048.470504] RSP: 0018:acebc7877ca8 EFLAGS: 0002 [56048.470505] RAX: 0101 RBX: 0246 RCX: 001f [56048.470505] RDX: RSI: RDI: 94dcf5341dc0 [56048.470506] RBP: 94dcf534 R08: 0002 R09: 00029600 [56048.470506] R10: 60d29656a45c R11: 94dcf534fd12 R12: 94dcf5341db0 [56048.470507] R13: 94dcf5341dc0 R14: 94dcc4ae8a00 R15: 0003 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470507] ? native_queued_spin_lock_slowpath+0x5d/0x1d0 [56048.470508] [56048.470508] _raw_spin_lock_irqsave+0x32/0x40 [56048.470509] lpfc_dmp_dbg.part.32+0x28/0x220 [lpfc] [56048.470509] lpfc_cmpl_els_fdisc+0x145/0x460 [lpfc] [56048.470509] lpfc_sli_cancel_jobs+0x92/0xd0 [lpfc] [56048.470510] lpfc_els_flush_cmd+0x43c/0x670 [lpfc] [56048.470510] lpfc_els_flush_all_cmd+0x37/0x60 [lpfc] [56048.470510] lpfc_sli4_async_event_proc+0x956/0x1720 [lpfc] [56048.470511] lpfc_do_work+0x1485/0x1d70 [lpfc] [56048.470511] ? __schedule+0x280/0x700 [56048.470511] ? finish_wait+0x80/0x80 [56048.470512] ? lpfc_unregister_unused_fcf+0x80/0x80 [lpfc] [56048.470512] kthread+0x112/0x130 [56048.470513] ? kthread_flush_work_fn+0x10/0x10 [56048.470513] ret_from_fork+0x1f/0x40 [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# - [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /etc/redhat-release Red Hat Enterprise Linux release 8.3 (Ootpa) [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/module/lpfc/version 0:14.0.390.2 [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/scsi_host/host*/modeldesc Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter Emulex LightPulse LPe32002-M2 2-Port 32Gb Fibre Channel Adapter [root@ms-svr3-10-231-131-160 127.0.0.1-2021-11-20-05:14:30]# cat /sys/class/scsi_host/host*/fwrev 14.0.390.1, sli-4:2:c 14.0.390.1, sli-4:2:c [root@ms-svr3-10-231-131-160
[Bug 1971151] Re: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
** Tags added: servcert-343 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971151 Title: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971193] Re: Server Crash while running IO and switch port bounce test with 2K login session
** Tags added: servcert-345 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971193 Title: Server Crash while running IO and switch port bounce test with 2K login session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
Hi Sumit, Can you file a separate bug for these new patches? The original patch set has been pulled and is in the process of being included in a kernel update and at this point these should be part of a new request. On Sun, May 1, 2022 at 20:16 Sumit Saxena <1967...@bugs.launchpad.net> wrote: > One more commit to be included: > ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header > scsi_bsg_mpi3mr.h > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1967116 > > Title: > [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Jammy: > Fix Committed > > Bug description: > Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04 > kernel. These patches got accepted by the upstream and please find the > corresponding commit IDs as below: > > 334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning > 22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0 > d44b5fefb22e scsi: mpi3mr: Fix memory leaks > 21401408ddeb scsi: mpi3mr: Update the copyright year > 999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size > b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever > 191a3ef58634 scsi: mpi3mr: Fix hibernation issue > 04b27e538d50 scsi: mpi3mr: Update MPI3 headers > 6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count > 580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event > 3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc > comments > 5867b8569e64 scsi: mpi3mr: Fix some spelling mistakes > c77b1f8a8fae scsi: mpi3mr: Bump driver version to 8.0.0.61.0 > a91603a5d504 scsi: mpi3mr: Enhanced Task Management Support Reply > handling > c86651345ca5 scsi: mpi3mr: Use TM response codes from MPI3 headers > afd3a5793fe2 scsi: mpi3mr: Add io_uring interface support in I/O-polled > mode > 95cca8d5542a scsi: mpi3mr: Print cable mngnt and temp threshold events > 78b76a0768ef scsi: mpi3mr: Support Prepare for Reset event > c1af985d27da scsi: mpi3mr: Add Event acknowledgment logic > c5758fc72b92 scsi: mpi3mr: Gracefully handle online FW update operation > b64845a7d403 scsi: mpi3mr: Detect async reset that occurred in firmware > c0b00a931e5e scsi: mpi3mr: Add IOC reinit function > fe6db6151565 scsi: mpi3mr: Handle offline FW activation in graceful > manner > 59bd9cfe3fa0 scsi: mpi3mr: Code refactor of IOC init - part2 > e3605f65ef69 scsi: mpi3mr: Code refactor of IOC init - part1 > a6856cc4507b scsi: mpi3mr: Fault IOC when internal command gets timeout > 2ac794baaec9 scsi: mpi3mr: Display IOC firmware package version > 13fd7b1555b6 scsi: mpi3mr: Handle unaligned PLL in unmap cmnds > 4f08b9637f63 scsi: mpi3mr: Increase internal cmnds timeout to 60s > ba68779a518d scsi: mpi3mr: Do access status validation before adding > devices > 17d6b9cf89cf scsi: mpi3mr: Add support for PCIe Managed Switch SES device > ec5ebd2c14a9 scsi: mpi3mr: Update MPI3 headers - part2 > d00ff7c31195 scsi: mpi3mr: Update MPI3 headers - part1 > fbaa9aa48bb4 scsi: mpi3mr: Don't reset IOC if cmnds flush with reset > status > a83ec831b24a scsi: mpi3mr: Replace spin_lock() with spin_lock_irqsave() > 9cf0666f34b1 scsi: mpi3mr: Add debug APIs based on logging_level bits > 30e99f05f8b1 scsi: mpi3mr: Use scnprintf() instead of snprintf() > 97e6ea6d7806 scsi: mpi3mr: Fix duplicate device entries when scanning > through sysfs > 1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly > 76a4f7cc5973 scsi: mpi3mr: Clean up mpi3mr_print_ioc_info() > 92cc94adfce4 scsi: mpi3mr: Use the proper SCSI midlayer interfaces for PI > 69868c3b6939 scsi: mpi3mr: Use scsi_cmd_to_rq() instead of > scsi_cmnd.request > aa0dc6a73309 scsi: mpi3mr: Fix W=1 compilation warnings > 62e528b80d6b scsi: mpi3mr: Fix warnings reported by smatch > a254eae30b45 scsi: mpi3mr: Fix error return code in mpi3mr_init_ioc() > f9dc034d0402 scsi: mpi3mr: Fix missing unlock on error > 2938bedd0efa scsi: mpi3mr: Fix error handling in mpi3mr_setup_isr() > d46bdecd9f3c scsi: mpi3mr: Delete unnecessary NULL check > d3d61f9c8c2d scsi: mpi3mr: Fix a double free > 7b8a49881b01 scsi: mpi3mr: Fix fall-through warning for Clang > 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints > > > Thanks, > Sumit > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967116/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main; > status=In Progress; importance=Undecided; assignee= > jeffrey.l...@canonical.com; > Launchpad-Bug: distribution=ubuntu; distroseries=jammy; > sourcepackage=linux; component=main; status=Fix Committed; > importance=Medium; assignee=jeffrey.l...@canonical.com; > Launchpad-Bug-Tags: servcert-230
[Bug 1946773] Re: "An error occurred. Press enter to start a shell"
>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. Fair enough. All I know is that I was unable to reproduce this even when mounting the ISO locally and going through three or four layers of web browser - BMC console - web browser - BMC console with desktop running on a server in the lab talking to another server in the lab. Latency is a problem, for sure. I tried doing this the other day by mounting that ISO on my local desktop and booting the machine from few hundred miles away on a 1.5Mb/s uplink and it was... not pleasant. I suspect Zhou Ling is doing this from a windows laptop over wifi through multiple layers of access point/router/switch (though the wifi is a suspicion, and I wonder if this goes away if Zhou Ling plugs that laptop into the same network the server BMC is on using a GigE dongle and some cat-5). Anyway, not my call to fix or not fix, it seemed to me that these were similar but not the same, but I am happy to be wrong on that. 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. -- 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"
One more comment, I cannot reproduce this. To test, I installed Ubuntu Desktop 20.04 LTS onto a SR645 in a rack in my DC. I then accessed that desktop, opened Firefox, and accessed the XCC on a SR670 V2. I mounted the ISO image using local media, and was able to boot the SR670 V2 using an ISO mounted locally via the XCC, and was able to successfully install 22.04 LTS. So the problem is in your environment somewhere. -- 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"
OK, so it works via remote media if you mount it locally using NFS. And does the same hold true for the 20.04.4 LTS Server Live ISO, and the 21.10 Server Live ISO? And can you install a desktop environment on a server next to the SR650 and on the same switch, rather than your laptop, and see if you can do this from one server to the next? And is your laptop using wifi or ethernet? If ethernet, is it using a built in RJ45 jack, or a USB dongle? Is that USB dongle USB2 or USB3, and is it plugged into a USB2 or USB3 port? I'm not seeing a problem here right now with the ISO or the installer, but it sounds much more like an environmental issue given that: 1: you can provide the ISO via NFS to the XCC and boot it 2: You cannot provide the ISO from your laptop to the XCC using locally mounted virtual media. Point is, I don't think the issue you're seeing is actually related to this bug at this point. -- 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 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04
Poked the Kernel Team to see if someone could take a look at this one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+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"
Given it took so long, are you sure you're not hitting some timeout that's unmounting the ISO? And can you put the ISO somewhere closer to the server? I've had success sharing it on an NFS share local to the server and mounting that via the XCC. -- 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 1968716] Re: The infiniband port can not display during ubuntu server 22.04 installation
Also, per your Comment #10 you have gone from teh ISO to PXE booting which are two different things... Have you tried this in MAAS? Does MAAS see the IB devices when commissioning, and can you deploy using the IB device to PXE via MAAS? ** Description changed: + SUMMARY: Jammy ISO is not loading ib_iboip module when a system contains + an Infiniband device. Also the ISO is missing the rdma-core stack that + is necessary for interacting with IB devices. + 1.Fresh install the ubuntu server 22.04 on Lenovo server with "ThinkSystem Mellanox ConnectX-6 HDR100/100GbE QSFP56 2-port PCIe VPI Adapter" and "infiniband mode" 2.The network port about infiniband(ibX) can not be found. 3.The network port can be found after finish the installation. The other info: The network port(ib0/ib1) can be detected during RHEL 8.5 installation -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968716 Title: The infiniband port can not display during ubuntu server 22.04 installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968716] Re: The infiniband port can not display during ubuntu server 22.04 installation
Is it possible to drop to a shell during the install and run `apport- collect 1968716` before you add the rdma-core and ib_ipoib modules? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968716 Title: The infiniband port can not display during ubuntu server 22.04 installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: Jeff Lane (bladernr) 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/1967116 Title: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819994] Re: cloud-init selects sysconfig netconfig renderer if network-manager is installed on Ubuntu
** Tags added: servcert-265 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819994 Title: cloud-init selects sysconfig netconfig renderer if network-manager is installed on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1819994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968952] Re: subiquity crash when install ubuntu server 22.04 on server with multiple adapter
Hi Shangsong, So what you seem to be saying, if I understand is that: Subiquity crashes if the machine has a connected network device with a valid IP but no external access Subiqutiy with NO connected network device successfully installs. Is that correct? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968952 Title: subiquity crash when install ubuntu server 22.04 on server with multiple adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1968952/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969477] Re: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection
>If direct access to Launchpad is blocked how was a bug report filed in the first place? Clicking the "Report a Bug" link on any project's page in LP. This is done from a machine outside of the airgapped or restricted access lab where the hardware sits. Also, I should point out (which I mentioned originally) that one can, and I'll also start suggesting they do this, use --save with ubuntu-bug to create a bug report that can be submitted later from a different machine. I'm just asking to have apport-collect also feature this... Perhaps the solution since, as you pointed out, apport needs to read the bug to know which package to collect files for, is to require the package as part of the commmand... e.g. apport-collect --save=/path/to/filename --package=$PACKAGE $BUG_NUMBER -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969477 Title: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1969477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967848] Re: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3
Did you try just copying the URL and accessing it from a different laptop? Alternately, you could, on the failing system run this: ubuntu-bug --save=~/1967848-apport-logs linux which will create a new bug report log file (there's, unfortunately, no way to use apport-collect and NOT submit from the machine itself). But you could then upload that created log file to this bug with just an explanation that you were unable to send those logs from within your test lab due to security restrictions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967848 Title: FLOGI failure and port state bypassed connecting to 3PAR storage on Ubuntu 18.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969477] [NEW] apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection
Public bug reported: We very often tell our hardware partners to "file a bug" when they encounter issues. This requires them to run apport-collect to gather and submit logs for the bug. However, very often, the hardware that has the problem is in a lab that has tight security restrictions and direct access to launchpad is blocked. This makes it nearly impossible for them to gather any requested logs, since apport-collect requires a direct line to Launchpad. apport-collect needs to adopt the --save feature of apport-bug/ubuntu- bug to save the prescribed logs and system data in a tarball that can then be attached to a bug after the fact. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.23 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportLog: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 19 10:25:54 2022 InstallationDate: Installed on 2016-02-11 (2258 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969477 Title: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1969477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Hi Sujith, have you been able to get the nvidia bug report log for them to help debug this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
This will hit the first SRU for 5.15. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967116 Title: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968104] Re: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk
As discussed elsewhere, These are warnings, not errors, and the only proposal to resolve this was rejected for solid reasons several years ago with no apparent follow-on attempts to resolve the root cause, there's not much we'll do here. It was said by Kernel that these are safe to ignore. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1968104 Title: [Ubuntu 22.04] dmesg shows "GPT:Primary header thinks Alt. header is not at the end of the disk" with installing OS in a SW RAID1 disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960364] Re: EDAC MCE updates for AMD Genoa in 22.04
Per Kim, this was a "Nice to have" rather than necessary patch set, so we'll pick this up in a future HWE. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1960364 Title: EDAC MCE updates for AMD Genoa in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968519] Re: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04
Just to be clear, when you say "Physical" do you have an actual monitor plugged into the VGA port, or are you using a KVM or remote KVM (not the XCC console, but an actual KVM device). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968519 Title: [Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer shows no signal (black screen) when install Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968716] Re: The infiniband port can not display during ubuntu server 22.04 installation
Adding a kernel task, two possible issues: 1: installer env is missing a driver 2: if the driver is loaded, does subiquity see and manage the device? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968716 Title: The infiniband port can not display during ubuntu server 22.04 installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968716] Re: The infiniband port can not display during ubuntu server 22.04 installation
can you boot the installer, drop to a shell before starting install, load ib_ipoib, and then does the installer see the IB device? ** Also 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/1968716 Title: The infiniband port can not display during ubuntu server 22.04 installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1968716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04
** Changed in: linux (Ubuntu Jammy) Assignee: Jeff Lane (bladernr) => Michael Reed (mreed8855) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965241 Title: Include DPC Fixes in Ubuntu 22.04 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1965241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
Sujith, Can you get a nvidia-bug-report.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950778] Re: Ubuntu 20.04.3 generates IO error message during FIO stress.
** Changed in: linux (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950778 Title: Ubuntu 20.04.3 generates IO error message during FIO stress. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968145] Re: Ubuntu won't change itself to first boot option in UEFI Boot Order after installing Ubuntu22.04
I'm pretty sure this is by design... a few years ago we hit issues where grub was setting Ubuntu as the primary boot device in EFI automatically, overriding user settings. For MAAS (for example, as this is where we were most impacted), MAAS works better if Network is always the first boot option. What would happen is that we'd install via MAAS, then the Ubuntu option would be injected and rewrite the EFI boot order and the machine was not able to be PXE booted after that when you wanted to release and re- deploy, because from that point onwards the machine would always boot from HDD first due to the location of the Ubuntu option. So I think this is probably by design, to avoid situations where installing ubuntu overrides user defined boot order. The presumption is that if you set PXE to be the first boot device in BIOS, you probably intend to always boot the machine via PXE, and if you want to vary that, you'll trigger the boot menu to choose a temporary alternative. Conversely, if you plan to mostly boot from ISO, you wouldn't want to waste your time waiting on PXE to time out, so you'd have set the boot order so that HDD/SSD comes first anyway. At least, that is my recollection, and as I said, I do think this is intended behaviour, but lets see if someone who manages Grub can comment on this. I'll escalate it to that team for visibility. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968145 Title: Ubuntu won't change itself to first boot option in UEFI Boot Order after installing Ubuntu22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1968145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968145] Re: Ubuntu won't change itself to first boot option in UEFI Boot Order after installing Ubuntu22.04
** Package changed: kernel-package (Ubuntu) => grub (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968145 Title: Ubuntu won't change itself to first boot option in UEFI Boot Order after installing Ubuntu22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub/+bug/1968145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967116 Title: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
5.19/scsi-staging as of 4/7/2022, need to wait until it at least merges into linux-next. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965927] Re: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches
** Tags added: servcert-234 ** Changed in: linux (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965927 Title: [Ubuntu 22.04] mpt3sas: Request to include latest bug fix patches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
Hi Sumit, could you please verify the test kernel here: https://kernel.ubuntu.com/~kmously/kernel-kmously-2e0820d-jmN7/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967116 Title: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937295 Title: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
HI Sujith, can you tell us what server this is, and how much RAM is in it? Just wondering. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917471] Re: [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which causes Bus Fatal Error when rebooting system with BCM5720 NIC
PR made for the Focal part of this -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917471 Title: [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which causes Bus Fatal Error when rebooting system with BCM5720 NIC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jeff Lane (bladernr) ** Description changed: + SRU Justification: + Impact: + Recovery from DownPort Containment events fail and the NVMe endpoint is not accessible in some scenarios. - Target kernels: 5.15 + Fix: + These are some of the DPC fixes which help in handling some of the + failure cases of DownPort Containment events. - - - - These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Without these, recovery from DPC event fails and NVMe endpoint is not accessible for some of the scenarios. - - Upstream kernel patches to be included into Ubuntu 22.04 SRU and into - Ubuntu 20.04.5: + Upstream kernel patches to be included into Ubuntu 22.04 and into Ubuntu + 20.04.5: Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4 Not yet pulled PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884 + + Test Case: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965241 Title: Include DPC Fixes in Ubuntu 22.04 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
This one is causing the kernel build to fail after pulling all of these into our 5.15 tree: 1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly Is there a missing patch in this set that perhaps sets up this one? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967116 Title: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
Linux Next 334ae6459aa3 scsi: mpi3mr: Fix flushing !WQ_MEM_RECLAIM events warning 22754f7fbb40 scsi: mpi3mr: Bump driver version to 8.0.0.68.0 d44b5fefb22e scsi: mpi3mr: Fix memory leaks 21401408ddeb scsi: mpi3mr: Update the copyright year 999224612724 scsi: mpi3mr: Fix reporting of actual data transfer size b3911ab3a76e scsi: mpi3mr: Fix cmnd getting marked as in use forever 191a3ef58634 scsi: mpi3mr: Fix hibernation issue 04b27e538d50 scsi: mpi3mr: Update MPI3 headers 6d211f1d2635 scsi: mpi3mr: Fix printing of pending I/O count 580e6742205e scsi: mpi3mr: Fix deadlock while canceling the fw event 5.17 Mainline 3bb3c24e268a scsi: mpi3mr: Fix formatting problems in some kernel-doc comments 5867b8569e64 scsi: mpi3mr: Fix some spelling mistakes c77b1f8a8fae scsi: mpi3mr: Bump driver version to 8.0.0.61.0 a91603a5d504 scsi: mpi3mr: Enhanced Task Management Support Reply handling c86651345ca5 scsi: mpi3mr: Use TM response codes from MPI3 headers afd3a5793fe2 scsi: mpi3mr: Add io_uring interface support in I/O-polled mode 95cca8d5542a scsi: mpi3mr: Print cable mngnt and temp threshold events 78b76a0768ef scsi: mpi3mr: Support Prepare for Reset event c1af985d27da scsi: mpi3mr: Add Event acknowledgment logic c5758fc72b92 scsi: mpi3mr: Gracefully handle online FW update operation b64845a7d403 scsi: mpi3mr: Detect async reset that occurred in firmware c0b00a931e5e scsi: mpi3mr: Add IOC reinit function fe6db6151565 scsi: mpi3mr: Handle offline FW activation in graceful manner 59bd9cfe3fa0 scsi: mpi3mr: Code refactor of IOC init - part2 e3605f65ef69 scsi: mpi3mr: Code refactor of IOC init - part1 a6856cc4507b scsi: mpi3mr: Fault IOC when internal command gets timeout 2ac794baaec9 scsi: mpi3mr: Display IOC firmware package version 13fd7b1555b6 scsi: mpi3mr: Handle unaligned PLL in unmap cmnds 4f08b9637f63 scsi: mpi3mr: Increase internal cmnds timeout to 60s ba68779a518d scsi: mpi3mr: Do access status validation before adding devices 17d6b9cf89cf scsi: mpi3mr: Add support for PCIe Managed Switch SES device ec5ebd2c14a9 scsi: mpi3mr: Update MPI3 headers - part2 d00ff7c31195 scsi: mpi3mr: Update MPI3 headers - part1 fbaa9aa48bb4 scsi: mpi3mr: Don't reset IOC if cmnds flush with reset status a83ec831b24a scsi: mpi3mr: Replace spin_lock() with spin_lock_irqsave() 9cf0666f34b1 scsi: mpi3mr: Add debug APIs based on logging_level bits 5.16 Mainline 30e99f05f8b1 scsi: mpi3mr: Use scnprintf() instead of snprintf() 1a30fd18f21b scsi: mpi3mr: Call scsi_done() directly 76a4f7cc5973 scsi: mpi3mr: Clean up mpi3mr_print_ioc_info() Ubuntu-5.15.0 - no need to pull 97e6ea6d7806 scsi: mpi3mr: Fix duplicate device entries when scanning through sysfs 92cc94adfce4 scsi: mpi3mr: Use the proper SCSI midlayer interfaces for PI 69868c3b6939 scsi: mpi3mr: Use scsi_cmd_to_rq() instead of scsi_cmnd.request aa0dc6a73309 scsi: mpi3mr: Fix W=1 compilation warnings 62e528b80d6b scsi: mpi3mr: Fix warnings reported by smatch a254eae30b45 scsi: mpi3mr: Fix error return code in mpi3mr_init_ioc() f9dc034d0402 scsi: mpi3mr: Fix missing unlock on error 2938bedd0efa scsi: mpi3mr: Fix error handling in mpi3mr_setup_isr() d46bdecd9f3c scsi: mpi3mr: Delete unnecessary NULL check d3d61f9c8c2d scsi: mpi3mr: Fix a double free 7b8a49881b01 scsi: mpi3mr: Fix fall-through warning for Clang 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967116 Title: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967116] Re: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
** Tags added: servcert-230 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967116 Title: [Ubuntu 22.04] mpi3mr: Request to include latest bug fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
** Also affects: snapd 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/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
** Changed in: systemd (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1966203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966203] Re: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04
Can this be reproduced in EFI mode, or is it only when in Legacy Mode? ALso, what is the mount command you are using? Just basic like "mount /dev/device /mountpoint"? Or is there a different mount command you are using that is failing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966203 Title: Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with exit code 1." in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1966203/+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
** Tags added: soa -- 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 1917471] Re: [SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which causes Bus Fatal Error when rebooting system with BCM5720 NIC
** Description changed:
SRU Justification:
[IMPACT]
This is being reported by a hardware partner as it is being noticed a
lot both in their internal testing teams and also being reported with
some frequency by customers who are seeing these messages in their logs
and thus it is generating an unusualy high volume of support calls from
the field.
In 5.4, commit d60cd06331a3566d3305b3c7b566e79edf4e2095 was introduced
upstream and pulled into Ubuntu between 5.4.0-58.64 and 5.4.0-59.65.
Upstream, these errors were discovered and that patch was reverted (see
Fix Below). We carry the revert commit in all subsequent Focal HWE
kernels starting at 5.12, but the fix was never pulled back into Focal
5.4.
according to the hardware partner:
the following error messages are observed when rebooting a machine that
uses the BCM5720 chipset, which is a widely used 1GbE controller found
on LOMs and OCP NICs as well as many PCIe NIC models.
[ 146.429212] shutdown[1]: Rebooting.
[ 146.435151] kvm: exiting hardware virtualization
[ 146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x4009
[ 148.088133] [qede_unload:2236(eno12409)]Link is down
[ 148.183618] qede :31:00.1: Ending qede_remove successfully
[ 148.518541] [qede_unload:2236(eno12399)]Link is down
[ 148.625066] qede :31:00.0: Ending qede_remove successfully
[ 148.762067] ACPI: Preparing to enter system sleep state S5
[ 148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 148.803731] {1}[Hardware Error]: event severity: recoverable
[ 148.810191] {1}[Hardware Error]: Error 0, type: fatal
[ 148.816088] {1}[Hardware Error]: section_type: PCIe error
[ 148.822391] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 148.829026] {1}[Hardware Error]: version: 3.0
[ 148.834266] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 148.841140] {1}[Hardware Error]: device_id: :04:00.0
[ 148.847309] {1}[Hardware Error]: slot: 0
[ 148.852077] {1}[Hardware Error]: secondary_bus: 0x00
[ 148.857876] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 148.865145] {1}[Hardware Error]: class_code: 02
[ 148.870845] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 148.879842] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 148.886575] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask:
0x0001
[ 148.902795] tg3 :04:00.0: AER:[20] UnsupReq (First)
[ 148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer,
aer_agent=Requester ID
[ 148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
[ 148.925558] tg3 :04:00.0: AER: TLP Header: 4001 030f
90028090
[ 148.933984] reboot: Restarting system
[ 148.938319] reboot: machine restart
The hardware partner did some bisection and observed the following:
Kernel version Fatal Error
5.4.0-42.46 No
5.4.0-45.49 No
5.4.0-47.51 No
5.4.0-48.52 No
5.4.0-51.56 No
5.4.0-52.57 No
5.4.0-53.59 No
5.4.0-54.60 No
5.4.0-58.64 No
5.4.0-59.65 yes
5.4.0-60.67 yes
[FIX]
The fix is to apply this patch from upstream:
commit 9d3fcb28f9b9750b474811a2964ce022df56336e
Author: Josef Bacik
Date: Tue Mar 16 22:17:48 2021 -0400
- Revert "PM: ACPI: reboot: Use S5 for reboot"
-
- This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.
-
- This patch causes a panic when rebooting my Dell Poweredge r440. I do
- not have the full panic log as it's lost at that stage of the reboot and
- I do not have a serial console. Reverting this patch makes my system
- able to reboot again.
+ Revert "PM: ACPI: reboot: Use S5 for reboot"
+
+ This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.
+
+ This patch causes a panic when rebooting my Dell Poweredge r440. I do
+ not have the full panic log as it's lost at that stage of the reboot and
+ I do not have a serial console. Reverting this patch makes my system
+ able to reboot again.
Example:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1917471
- [TEST CASE]
+ The hardware partner has preemptively pulled our 5.4 tree, applied the
+ fix and tested it in their labs and determined that this does resolve
+ the issue.
+
+ [TEST CASE]
Install the patched kernel on a machine that uses a BCM5720 LOM and reboot
the machine and see that the errors no longer appear.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917471
Title:
[SRU][Regression] Revert "PM: ACPI: reboot: Use S5 for reboot" which
[Bug 1917471] Re: [Regression] Bus Fatal Error observed when reboot on BCM5720
** Description changed:
- impact
- being noticed a lot, only affects 5.4, fix in subsequent failures
+ SRU Justification:
- The offending patch was removed in 20.10 and later kernels (it was
- reverted upstream not long after being merged into mainline but we never
- reverted it)
+ [IMPACT]
+ This is being reported by a hardware partner as it is being noticed a
+ lot both in their internal testing teams and also being reported with
+ some frequency by customers who are seeing these messages in their logs
+ and thus it is generating an unusualy high volume of support calls from
+ the field.
- following error messages are observed
+ In 5.4, commit d60cd06331a3566d3305b3c7b566e79edf4e2095 was introduced
+ upstream and pulled into Ubuntu between 5.4.0-58.64 and 5.4.0-59.65.
+ Upstream, these errors were discovered and that patch was reverted (see
+ Fix Below). We carry the revert commit in all subsequent Focal HWE
+ kernels starting at 5.12, but the fix was never pulled back into Focal
+ 5.4.
+
+ according to the hardware partner:
+
+ the following error messages are observed when rebooting a machine that
+ uses the BCM5720 chipset, which is a widely used 1GbE controller found
+ on LOMs and OCP NICs as well as many PCIe NIC models.
[ 146.429212] shutdown[1]: Rebooting.
[ 146.435151] kvm: exiting hardware virtualization
[ 146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x4009
[ 148.088133] [qede_unload:2236(eno12409)]Link is down
[ 148.183618] qede :31:00.1: Ending qede_remove successfully
[ 148.518541] [qede_unload:2236(eno12399)]Link is down
[ 148.625066] qede :31:00.0: Ending qede_remove successfully
[ 148.762067] ACPI: Preparing to enter system sleep state S5
[ 148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 148.803731] {1}[Hardware Error]: event severity: recoverable
[ 148.810191] {1}[Hardware Error]: Error 0, type: fatal
[ 148.816088] {1}[Hardware Error]: section_type: PCIe error
[ 148.822391] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 148.829026] {1}[Hardware Error]: version: 3.0
[ 148.834266] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 148.841140] {1}[Hardware Error]: device_id: :04:00.0
[ 148.847309] {1}[Hardware Error]: slot: 0
[ 148.852077] {1}[Hardware Error]: secondary_bus: 0x00
[ 148.857876] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 148.865145] {1}[Hardware Error]: class_code: 02
[ 148.870845] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 148.879842] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 148.886575] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask:
0x0001
[ 148.902795] tg3 :04:00.0: AER:[20] UnsupReq (First)
[ 148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer,
aer_agent=Requester ID
[ 148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
[ 148.925558] tg3 :04:00.0: AER: TLP Header: 4001 030f
90028090
[ 148.933984] reboot: Restarting system
[ 148.938319] reboot: machine restart
- I have observed the following. when I test older kernel
+ The hardware partner did some bisection and observed the following:
Kernel version Fatal Error
5.4.0-42.46 No
5.4.0-45.49 No
5.4.0-47.51 No
5.4.0-48.52 No
5.4.0-51.56 No
5.4.0-52.57 No
5.4.0-53.59 No
5.4.0-54.60 No
5.4.0-58.64 No
5.4.0-59.65 yes
5.4.0-60.67 yes
- later I have bisect kernel between 5.4.0-58.64 and 5.4.0-59.65.
+ [FIX]
+ The fix is to apply this patch from upstream:
- looks like due to the following patch we are observing this issue. The
- driver is not handling D3 state properly
+ commit 9d3fcb28f9b9750b474811a2964ce022df56336e
+ Author: Josef Bacik
+ Date: Tue Mar 16 22:17:48 2021 -0400
- PCI/ACPI: Whitelist hotplug ports for D3 if power managed by ACPI
+ Revert "PM: ACPI: reboot: Use S5 for reboot"
+
+ This reverts commit d60cd06331a3566d3305b3c7b566e79edf4e2095.
+
+ This patch causes a panic when rebooting my Dell Poweredge r440. I do
+ not have the full panic log as it's lost at that stage of the reboot and
+ I do not have a serial console. Reverting this patch makes my system
+ able to reboot again.
- https://kernel.ubuntu.com/git/ubuntu/ubuntu-
- focal.git/commit/?id=b9319dd02269593911403dd5d684368bcef3261d
+ Example:
+
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1917471
+
+ [TEST CASE]
+ Install the patched kernel on a machine that uses a BCM5720 LOM and reboot
the machine and see that the errors no longer appear.
** Summary changed:
- [Regression] Bus Fatal Error observed when reboot on BCM5720
+
[Bug 1958623] Re: encounter RSOD while pxe booting from MaaS server
** Tags added: servcert-228 ** Tags removed: servcert-224 servcert-225 servcert-226 servcert-227 servcert-228 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958623 Title: encounter RSOD while pxe booting from MaaS server To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1958623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958623] Re: encounter RSOD while pxe booting from MaaS server
** Tags added: servcert-227 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958623 Title: encounter RSOD while pxe booting from MaaS server To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1958623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958623] Re: encounter RSOD while pxe booting from MaaS server
** Tags added: servcert-224 ** Tags added: servcert-225 ** Tags added: servcert-226 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958623 Title: encounter RSOD while pxe booting from MaaS server To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1958623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
** Changed in: linux (Ubuntu) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948636] Re: Ubuntu 22.04 Feature Request-NVMe: Include libnvme package
** Changed in: linux (Ubuntu Jammy) 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/1948636 Title: Ubuntu 22.04 Feature Request-NVMe: Include libnvme package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965241] Re: Include DPC Fixes in Ubuntu 22.04 and 20.04
** Description changed: - These are some of the DPC fixes which help in handling some of the - failure cases of DownPort Containment events. Without these, recovery - from DPC event fails and NVMe endpoint is not accessible for some of the - scenarios. + Impact: + + Target kernels: 5.15 + + + + + + These are some of the DPC fixes which help in handling some of the failure cases of DownPort Containment events. Without these, recovery from DPC event fails and NVMe endpoint is not accessible for some of the scenarios. Upstream kernel patches to be included into Ubuntu 22.04 SRU and into Ubuntu 20.04.5: + Already in Jammy as of Ubuntu-5.15.0-1.1 PCI/portdrv: Enable Bandwidth Notification only if port supports it https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=00823dcbdd415c868390feaca16f0265101efab4 + Not yet pulled PCI: pciehp: Ignore Link Down/Up caused by error-induced Hot Reset https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.17-rc6=ea401499e943c307e6d44af6c2b4e068643e7884 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965241 Title: Include DPC Fixes in Ubuntu 22.04 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917471] Re: [Regression] Bus Fatal Error observed when reboot on BCM5720
** Description changed:
+ impact
+ being noticed a lot, only affects 5.4, fix in subsequent failures
+
+ The offending patch was removed in 20.10 and later kernels (it was
+ reverted upstream not long after being merged into mainline but we never
+ reverted it)
+
+
following error messages are observed
[ 146.429212] shutdown[1]: Rebooting.
[ 146.435151] kvm: exiting hardware virtualization
[ 146.575319] megaraid_sas :67:00.0: megasas_disable_intr_fusion is
called outbound_intr_mask:0x4009
[ 148.088133] [qede_unload:2236(eno12409)]Link is down
[ 148.183618] qede :31:00.1: Ending qede_remove successfully
[ 148.518541] [qede_unload:2236(eno12399)]Link is down
[ 148.625066] qede :31:00.0: Ending qede_remove successfully
[ 148.762067] ACPI: Preparing to enter system sleep state S5
[ 148.794638] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 5
[ 148.803731] {1}[Hardware Error]: event severity: recoverable
[ 148.810191] {1}[Hardware Error]: Error 0, type: fatal
[ 148.816088] {1}[Hardware Error]: section_type: PCIe error
[ 148.822391] {1}[Hardware Error]: port_type: 0, PCIe end point
[ 148.829026] {1}[Hardware Error]: version: 3.0
[ 148.834266] {1}[Hardware Error]: command: 0x0006, status: 0x0010
[ 148.841140] {1}[Hardware Error]: device_id: :04:00.0
[ 148.847309] {1}[Hardware Error]: slot: 0
[ 148.852077] {1}[Hardware Error]: secondary_bus: 0x00
[ 148.857876] {1}[Hardware Error]: vendor_id: 0x14e4, device_id: 0x165f
[ 148.865145] {1}[Hardware Error]: class_code: 02
[ 148.870845] {1}[Hardware Error]: aer_uncor_status: 0x0010,
aer_uncor_mask: 0x0001
[ 148.879842] {1}[Hardware Error]: aer_uncor_severity: 0x000ef030
[ 148.886575] {1}[Hardware Error]: TLP Header: 4001 030f 90028090
[ 148.894823] tg3 :04:00.0: AER: aer_status: 0x0010, aer_mask:
0x0001
[ 148.902795] tg3 :04:00.0: AER:[20] UnsupReq (First)
[ 148.910234] tg3 :04:00.0: AER: aer_layer=Transaction Layer,
aer_agent=Requester ID
[ 148.918806] tg3 :04:00.0: AER: aer_uncor_severity: 0x000ef030
[ 148.925558] tg3 :04:00.0: AER: TLP Header: 4001 030f
90028090
[ 148.933984] reboot: Restarting system
[ 148.938319] reboot: machine restart
-
- I have observed the following. when I test older kernel
-
+ I have observed the following. when I test older kernel
Kernel version Fatal Error
5.4.0-42.46 No
5.4.0-45.49 No
5.4.0-47.51 No
5.4.0-48.52 No
5.4.0-51.56 No
5.4.0-52.57 No
5.4.0-53.59 No
5.4.0-54.60 No
5.4.0-58.64 No
5.4.0-59.65 yes
5.4.0-60.67 yes
-
later I have bisect kernel between 5.4.0-58.64 and 5.4.0-59.65.
looks like due to the following patch we are observing this issue. The
driver is not handling D3 state properly
PCI/ACPI: Whitelist hotplug ports for D3 if power managed by ACPI
https://kernel.ubuntu.com/git/ubuntu/ubuntu-
focal.git/commit/?id=b9319dd02269593911403dd5d684368bcef3261d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917471
Title:
[Regression] Bus Fatal Error observed when reboot on BCM5720
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917471/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917471] Re: [Regression] Bus Fatal Error observed when reboot on BCM5720
The patch you're requesting reverts this patch: commit d60cd06331a3566d3305b3c7b566e79edf4e2095 Author: Kai-Heng Feng Date: Fri Oct 30 15:06:57 2020 +0800 PM: ACPI: reboot: Use S5 for reboot After reboot, it's not possible to use hotkeys to enter BIOS setup and boot menu on some HP laptops. BIOS folks identified the root cause is the missing _PTS call, and BIOS is expecting _PTS to do proper reset. Using S5 for reboot is default behavior under Windows, "A full shutdown (S5) occurs when a system restart is requested" [1], so let's do the same here. [1] https://docs.microsoft.com/en-us/windows/win32/power/system-power-states Signed-off-by: Kai-Heng Feng [ rjw: Subject edit ] Signed-off-by: Rafael J. Wysocki It looks like this was applied to 5.4 and the patch that reverts this was pulled into 5.13 and later, so that is why 5.4 is the only affected version. I was confused as to why this wasn't also appearing in Impish and Jammy. Now we know. So I can close those tasks. ** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Jammy) 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/1917471 Title: [Regression] Bus Fatal Error observed when reboot on BCM5720 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917471] Re: [Regression] Bus Fatal Error observed when reboot on BCM5720
** Project changed: linux => linux (Ubuntu) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Jeff Lane (bladernr) ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) 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/1917471 Title: [Regression] Bus Fatal Error observed when reboot on BCM5720 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917471] Re: [Regression] Bus Fatal Error observed when reboot on BCM5720
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917471 Title: [Regression] Bus Fatal Error observed when reboot on BCM5720 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1917471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
** Changed in: linux (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: dellserver Status: New => 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/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934620] Re: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS
** Description changed: - Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. + Installing NVidia A100-80GB GPUs in R750XA fails to initialize BAR memory space for GPUs. Multiple error messages in kernel.log file. + + Summary: + * Dell prefers to set SRIOV to disabled in bios globally + * This bug does not occur IF: + SRIOV is enabled in BIOS OR + "pci=realloc=off" is passed to the kernel at boot time + * This bug only affects systems with NVIDIA A100-80GB GPUs, it does not + affect systems with NVIDIA A100-40GB GPUs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934620 Title: NVIDIA A100-80GB GPU fails to initialize in R750xa, BAR Address setup failed if SR-IOV is disabled in BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1934620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951111] Re: [Jammy] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.3 for Ubuntu 22.04
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/195 Title: [Jammy] Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.3 for Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940112] Re: missing dependency of qemu-efi-aarch64 when testing arm platforms
** Tags added: servcert-216 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940112 Title: missing dependency of qemu-efi-aarch64 when testing arm platforms To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1940112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868708] Re: mdmon: device descriptor is not closed
** Changed in: mdadm (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: mdadm (Ubuntu Impish) Status: Fix Committed => 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/1868708 Title: mdmon: device descriptor is not closed To manage notifications about this bug go to: https://bugs.launchpad.net/mdadm/+bug/1868708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888812] Re: mdmonitor doesn't start recovery immediately
** Changed in: mdadm (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: mdadm (Ubuntu Impish) Status: Fix Committed => 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/112 Title: mdmonitor doesn't start recovery immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956982] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
test kernels can be found for now here: https://people.canonical.com/~jlane/kernels/1956982/ I've built those this morning as the patches have landed in the Jammy kernel tree but have yet to be built into the next binary due to delays in the kernel release. So for now, that should be sufficient to test, it's a straight build of the 5.15 tree as of this morning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956982 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956982] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956982 Title: Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948636] Re: Ubuntu 22.04 Feature Request-NVMe: Include libnvme package
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => New ** Tags added: soa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948636 Title: Ubuntu 22.04 Feature Request-NVMe: Include libnvme package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948644] Re: Ubuntu 22.04 Feature Request-Include python-dasbus pacakge
$ rmadison python3-dasbus python3-dasbus | 1.6-2 | jammy/universe | all Already exists in Jammy ** Changed in: linux (Ubuntu Jammy) Status: Incomplete => Fix Released ** Also affects: dasbus (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Jammy) ** Changed in: dasbus (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: dasbus (Ubuntu Jammy) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948644 Title: Ubuntu 22.04 Feature Request-Include python-dasbus pacakge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dasbus/+bug/1948644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948644] Re: Ubuntu 22.04 Feature Request-Include python-dasbus pacakge
you want python2 libraries? or do you mean python3-dasbus? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948644 Title: Ubuntu 22.04 Feature Request-Include python-dasbus pacakge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dasbus/+bug/1948644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948626] Re: Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
Is there a different staging kernel upstream where these have been merged? Also, it's too late to get nvme-stas and libnvme updated without a Feature Freeze Exception. Please work with Michael on that... it may be that we'll need to deal with this after release though, it's really late in the cycle at this point if we can't get the kernel patches in, there's no reason to hurry on the others. BUT we can at least see if we can get a FFE for libnvme and nvme-stas. You say "get the latest" but we only pull from Debian for userspace stuff normally. Without me looking, what is the timeline to getting these updated in Debian? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948626 Title: Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948626] Re: Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010
Doesn't look like any of those patches have been accepted upstream yet at all. at least I was unable to find any hint of hte kernel patches in mainline nor the torvalds tree. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948626 Title: Ubuntu 22.04 Feature Request-Add support for a NVMe-oF-TCP CDC Client - TP 8010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1948626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963283] Re: pci.ids needs to be kept current in active releases
** Attachment added: "Screenshot from 2022-03-03 17-25-53.png" https://bugs.launchpad.net/ubuntu/+source/pci.ids/+bug/1963283/+attachment/5565317/+files/Screenshot%20from%202022-03-03%2017-25-53.png ** Description changed: Currently, this is the state of the PCI ID database file in Ubuntu: $ rmadison pci.ids - pci.ids | 0.0~2020.03.20-1 | focal | source, all - pci.ids | 0.0~2021.08.22-1 | impish | source, all - pci.ids | 0.0~2022.01.22-1 | jammy | source, all + pci.ids | 0.0~2020.03.20-1 | focal | source, all + pci.ids | 0.0~2021.08.22-1 | impish | source, all + pci.ids | 0.0~2022.01.22-1 | jammy | source, all Because of this, focal installations cannot identify PCI devices that were added to the IDs file after March 20, 2020. As this is just a text file, pci.ids should always be updated with the latest info regardless of release. This has an effect on MAAS in which any hardware commissioned in MAAS uses a 2 year old version of hte PCIID database and thus cannot identify newer hardware such as the nVidia A100 GPU. The 2020 version of the file does not contain id's for this while the 2022 version in Jammy does: 12393 20f1 GA100 [A100 PCIe 40GB] + + + Comparing the current source to the version in focal, there are over 3500 additional or modified IDs in the id file: + + $ diff /usr/share/misc/pci.ids pci.ids |wc -l + 3529 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1963283 Title: pci.ids needs to be kept current in active releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pci.ids/+bug/1963283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963283] [NEW] pci.ids needs to be kept current in active releases
Public bug reported: Currently, this is the state of the PCI ID database file in Ubuntu: $ rmadison pci.ids pci.ids | 0.0~2020.03.20-1 | focal | source, all pci.ids | 0.0~2021.08.22-1 | impish | source, all pci.ids | 0.0~2022.01.22-1 | jammy | source, all Because of this, focal installations cannot identify PCI devices that were added to the IDs file after March 20, 2020. As this is just a text file, pci.ids should always be updated with the latest info regardless of release. This has an effect on MAAS in which any hardware commissioned in MAAS uses a 2 year old version of hte PCIID database and thus cannot identify newer hardware such as the nVidia A100 GPU. The 2020 version of the file does not contain id's for this while the 2022 version in Jammy does: 12393 20f1 GA100 [A100 PCIe 40GB] Comparing the current source to the version in focal, there are over 3500 additional or modified IDs in the id file: $ diff /usr/share/misc/pci.ids pci.ids |wc -l 3529 ** Affects: pci.ids (Ubuntu) Importance: Undecided Status: New ** Affects: pci.ids (Ubuntu Focal) Importance: Undecided Status: New ** Affects: pci.ids (Ubuntu Impish) Importance: Undecided Status: New ** Affects: pci.ids (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: pci.ids (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pci.ids (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: pci.ids (Ubuntu Impish) 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/1963283 Title: pci.ids needs to be kept current in active releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pci.ids/+bug/1963283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962143] Re: [Ubuntu 22.04] "TSC calibration failed" is shown in dmesg
*** This bug is a duplicate of bug 1953731 *** https://bugs.launchpad.net/bugs/1953731 ** This bug has been marked a duplicate of bug 1953731 Jammy update: v5.15.7 upstream stable release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962143 Title: [Ubuntu 22.04] "TSC calibration failed" is shown in dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961758] Re: Fail to run tpm2 command under ubuntu server 22.04
** Tags added: hwcert-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961758 Title: Fail to run tpm2 command under ubuntu server 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tpm2-tss-engine/+bug/1961758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962185] Re: Add ConnectX7 support and bug fixes to Jammy
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962185 Title: Add ConnectX7 support and bug fixes to Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958623] Re: encounter RSOD while pxe booting from MaaS server
@julian I added focal and bionic tasks per your comment #10, should we rewrite this as an SRU bug now, or would you ratner a separate SRU bug to handle focal and bionic? ** Also affects: grub2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: grub2 (Ubuntu Bionic) 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/1958623 Title: encounter RSOD while pxe booting from MaaS server To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1958623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1960926] Re: [VROC] Installation on RAID volume fails - ubuntu 22.04
hrmm so is the fix here then an update to subiquity to change how it gets array data? or is there a reversion or change needed for madam instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960926 Title: [VROC] Installation on RAID volume fails - ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1960926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
Marking it invalid for subiquity, since they seem pretty confident this is a kernel problem rather than a subiquity one. ** Changed in: subiquity 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/1937295 Title: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1937295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
