[Bug 2069961] Re: turbostat and powerstat not working on 22.04
bladernr@galactica:~/development/kernels/upstream/mainline$ git describe 3ac1d14d0583a v6.7-2-g3ac1d14d0583 So we will have to also pull this back to Mantic as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2069961 Title: turbostat and powerstat not working on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2069961] Re: turbostat and powerstat not working on 22.04
Thanks Kim, When you say 22.04, I presume this means 22.04 GA kernel (or 5.15)? ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) 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/2069961 Title: turbostat and powerstat not working on 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069961/+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
I had mentioned this in the meeting last time, but don't seen an update here... but a couple things: 1:IIRC this is the latest generation server and XCC with the latest XCC and UEFI firmware. Does this ALSO happen on the last generation hardware with older versions of XCC and UEFI firmware? 2. On this machine, what is the graphics device (most servers use something like an MGA G200, but I know you also have some machines that use Intel client CPUs (the Server versions of client platforms) that use the intel graphics device, IIRC. So what is the graphics device here, for clarity. (I see it is an SR650 V3, so I resume it's the Matrix G200, but wanted to confirm that). -- 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 2062568] Re: nfsd gets unresponsive after some hours of operation
The tricky part for me is that client was regularly changing, so I can't confidently say when did errors start appearing, it's just very suspicious that it needs high load (as new host and higher network bandwidth made the issue more frequent), and uploading to the server as just pure downloading doesn't seem to be a problem even if cached data is getting sent at full bandwidth for minutes. Moved the server to 24.04, but I've also moved some I/O heavy tasks to it so there would be less need of uploading. Client was on 23.10 and I'm still holding back on upgrading for some more weeks. Can't say a whole lot about the current situation as I'm not uploading much anymore to avoid the issue, but I actually ran into a hanging issue a few days ago, I just didn't have time to debug it, but the server didn't want to gracefully restart, so ended up hard rebooting. I believe it was the first time since moving I/O heavy tasks, wanted to upload a few hundred GiB of data back to the server which was downloaded from there a while ago without problems. Otherwise light I/O doesn't seem to run into this problem, like the occasional backup to the server is fine, but that rarely saturates the network, and likely completely fits into the page cache almost every time. A few hopefully helpful points for reproducing the problem: - As mentioned multiple times, download alone seems to be unaffected, uploading is what should be stressed, and I suspect that either there's no need to download at the same time, or just casual filesystem browsing is a good enough load. - A fast client with high bandwidth is key. Ran into this issue a couple times with an older host on 1 Gb/s, but a new fast host with 2.5 Gb/s made the issue appear significantly more frequently. - Likely doesn't matter how the link gets saturated, but I either processed files cached on the server (mixed R/W), or uploaded cached files (fast SSD should be fine too), meaning that the bottleneck was always the network at least while the caches were large enough. - Files were large, so there wasn't any stopping for fiddling with metadata as it would happen with small files, and the page cache was often exhausted. The target was a single HDD the majority of the time which often meant that writes started blocking (100-ish MiB/s HDD catching up with close to 250 MiB/s data), occasionally making the hosts freeze as the kernel's background I/O handling is still bad, we just pretend the issue is gone with SSDs being fast enough not to run into this. The page cache draining freezes may be good at exposing race conditions. It may be more efficient to start looking for what's causing the "RPC: Could not send backchannel reply error: -110" log spam which might be related. The lockup may take significant time to catch while that kernel message showed up quite frequently. Even now I have plenty of those lines without experiencing issues and not even uploading much, mostly just downloading large files. Some extra info which may or may not matter: - The server hardware is quite weak with an old 4 core Broadwell CPU, possibly helping to expose race condition problems - All file systems are Btrfs with noatime,discard=async,compress-force=zstd , the later part surely adding more load - LUKS is used everywhere, also adding some extra load - There's a Btrfs (on LUKS) image mounted over NFS (with not a whole lot of usage though) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062568 Title: nfsd gets unresponsive after some hours of operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2062568/+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
** 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 2067790] [NEW] package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
Public bug reported: error during update ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jun 1 10:47:16 2024 ErrorMessage: vereistenproblemen - blijft ongeconfigureerd InstallationDate: Installed on 2024-02-01 (120 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.12 SourcePackage: linux-restricted-modules-hwe-6.5 Title: package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-restricted-modules-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067790 Title: package linux-modules-nvidia-470-6.5.0-27-generic 6.5.0-27.28~22.04.1+2 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-hwe-6.5/+bug/2067790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058395] Re: pbuilder-dist noble create fails on jammy
Another workaround: On jammy I am able to use `pbuilder-dist noble amd64 build myproject.dsc` without the warning prompt if I first make a symlink: ``` cd /usr/share/debootstrap/scripts sudo ln -s gutsy noble ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058395 Title: pbuilder-dist noble create fails on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2058395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729433]
I was about to file a new one, and then I rediscovered the one that still describes the remaining problem: bug #99112 It was a bit difficult to find, so I will update its metadata a bit to relate to this. I'll leave you to decide whether its importance/priority should be bumped from "low" to "high" to match this closed bug here or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729433 Title: LibreOffice doesn't remember window size when running under Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062568] Re: nfsd gets unresponsive after some hours of operation
** Attachment added: "rpc_tasks.txt" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2062568/+attachment/5770302/+files/rpc_tasks.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062568 Title: nfsd gets unresponsive after some hours of operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2062568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062568] Re: nfsd gets unresponsive after some hours of operation
Oh fun, trying to add multiple attachments, I just ended up finding a bug report from 2007 complaining about apport being able to do this, but the web interface is limited, so guess I'll get a bit spammy. Ran into the same as usual again, even with avoiding heavy utilization. Not seeing anything too interesting in the gathered info and apparently the kernel log buffer is not large enough to be able to completely handle a task list dump, but seems like most of the information is at least there. Will try to use RPCNFSDCOUNT=1 for some time in case this is a silly deadlock, at least it's definitely easier to give it a try than to downgrade to Ubuntu 22.04 which worked well. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2062568/+attachment/5770300/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062568 Title: nfsd gets unresponsive after some hours of operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2062568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062568] Re: nfsd gets unresponsive after some hours of operation
** Attachment added: "nfs_threads.txt" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2062568/+attachment/5770301/+files/nfs_threads.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062568 Title: nfsd gets unresponsive after some hours of operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2062568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062406] Re: CVE-2024-32462: Sandbox escape via RequestBackground portal and CWE-88
While I'm not fully familiar with how things are done here, is it really sensible that the "Fix Released" status prevents search on the main page from even finding this issue? We aren't far from the upstream fixes being available for a week already without any of the supported releases of Ubuntu getting a fix, and even the visibility of the problem is significantly limited. It's a sandbox escape vulnerability, therefore privilege escalation. Upstream took it seriously, as smcv mentioned there are even multiple fixed versions to choose from to update to, but regular users don't even get to know that they have been affected by a vulnerability marked with high severity upstream for so long. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062406 Title: CVE-2024-32462: Sandbox escape via RequestBackground portal and CWE-88 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2062406/+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 2062568] Re: nfsd gets unresponsive after some hours of operation
Ran into this again just hours after commenting by attempting to unpack a large archive file. Apparently the new setup of higher performance host with more network bandwidth is just too overwhelming to be usable with NFS with this issue. Reading alone still seems to be fine though. Torturing 50% of the memory with memtester didn't reveal any problems, and getting the server to do the unpacking of files does the same mixed I/O with no issues so far, progressing way beyond where I could get over NFS, so it doesn't look like an HDD issue either. The info dumping described here seems to be potentially useful for the next catch, so linking it here: https://www.spinics.net/lists/linux-nfs/msg97486.html At some point I may try to reproduce the issue with just writing to see if the mixed workload is really required for the freeze, but not sure when will I get to it, can't just restart NFSd, and the mandatory reboot to get it going again is only feasible when all other tasks running on the host can be interrupted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062568 Title: nfsd gets unresponsive after some hours of operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2062568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062568] Re: nfsd gets unresponsive after some hours of operation
This kind of issue appeared with Ubuntu 23.10 for me on the server mostly using an HDD for bulk storage with a not exactly powerful CPU also being occupied with using WireGuard to secure the NFS connection. Mentioning the performance details because I have a feeling they matter. An also not exactly high performance client connecting over 1 Gb/s only very occasionally caused this problem, however given a 10 Gb/s connection, the issue appeared significantly more commonly. A higher performance setup utilizing a 2.5 Gb/s connection triggered this bug in a couple of days after setup. The lockup always seem to occur with heavy NFS usage, suspiciously mostly when there's both reading and writing going on, at least I don't recall it happening with reading only, but I'm not confident in stating it didn't happen with a writing only load. Found this bug report by the client error message, server side differs due to the different version: ``` [300146.04] INFO: task nfsd:1426 blocked for more than 241 seconds. [300146.046732] Not tainted 6.5.0-27-generic #28~22.04.1-Ubuntu [300146.046770] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [300146.046813] task:nfsdstate:D stack:0 pid:1426 ppid:2 flags:0x4000 [300146.046827] Call Trace: [300146.046832] [300146.046839] __schedule+0x2cb/0x750 [300146.046860] schedule+0x63/0x110 [300146.046870] schedule_timeout+0x157/0x170 [300146.046881] wait_for_completion+0x88/0x150 [300146.046894] __flush_workqueue+0x140/0x3e0 [300146.046908] nfsd4_probe_callback_sync+0x1a/0x30 [nfsd] [300146.047074] nfsd4_destroy_session+0x193/0x260 [nfsd] [300146.047219] nfsd4_proc_compound+0x3b7/0x770 [nfsd] [300146.047365] nfsd_dispatch+0xbf/0x1d0 [nfsd] [300146.047497] svc_process_common+0x420/0x6e0 [sunrpc] [300146.047695] ? __pfx_read_tsc+0x10/0x10 [300146.047706] ? __pfx_nfsd_dispatch+0x10/0x10 [nfsd] [300146.047848] ? __pfx_nfsd+0x10/0x10 [nfsd] [300146.047977] svc_process+0x132/0x1b0 [sunrpc] [300146.048157] nfsd+0xdc/0x1c0 [nfsd] [300146.048287] kthread+0xf2/0x120 [300146.048299] ? __pfx_kthread+0x10/0x10 [300146.048310] ret_from_fork+0x47/0x70 [300146.048321] ? __pfx_kthread+0x10/0x10 [300146.048331] ret_from_fork_asm+0x1b/0x30 [300146.048341] ``` This seems to be matching, but the previous lockups experienced may have been somewhat different. I mostly remember the client whining about the server not responding instead of the message presented here, and the server call trace used to have btrfs in it which made me suspect it may be exclusive to that, although the issue was always with NFS, nothing else locked up despite having some other sources of heavy I/O. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062568 Title: nfsd gets unresponsive after some hours of operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2062568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943480] Re: flatpak installation permission requirements different from ubuntu software
Can confirm the principle of least surprise being violated here. It took me getting a permission error trying to replace a file to test a bugfix to realize that: - Commands without explicit permission elevation do system-wide modifications - A theoretically user level setup is not fully covered by the backup of user files due to modifications escaping outside of the environment modifiable by the user - Storage usage sneaked out of the expected scope (home of the user). Not meaning just installed programs, but ".removed" and "repo" added up to double digit GiBs, towering above the "app" and "runtime" sizes the user is shown during installation The mentioned issues all stem from the problem that elevation is done with no notice and the usual barriers missing like either having to use sudo, or (worse case) being asked for a password instead of just denying the operation without being root. However, circumventing the password requirement for privilege escalation presents an interesting dilemma: - Either passwordless sudo is not a security issue as the user is expected to keep his account secure, and the additional obstacle of entering the password doesn't provide (much) security - Or the extra step of requiring a password can be relied on as a security feature, therefore a combo of app-uninstall + modify-repo + app-install with a malicious repository could be used for interactive privilege escalation in some cases Not completely on-topic, but as there's a divergence in privilege elevation here, I'll add an extra concern and question: As hardware security key support is starting to look good, how will it be possible to use one universally for privilege elevation? As I understand, PolKit is mostly independent from PAM, so merely requiring pam_u2f.so for sudo as a second factor might not provide any extra security if PolKit would be still okay with just the password. Can't say I'm a huge fan of PAM, but the centralized configuration surely seems to have an advantage, especially in such cases like this where a project is allowed to "slip" in rules lowering the security requirements for system modification. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943480 Title: flatpak installation permission requirements different from ubuntu software To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1943480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062406] Re: CVE-2024-32462: Sandbox escape via RequestBackground portal and CWE-88
Covering just Noble isn't really enough with Mantic and Jammy still providing vulnerable packages according to the advisory listing affected versions as: - < 1.10.9 - 1.12.x < 1.12.9 - 1.14.x < 1.14.6 - 1.15.x < 1.15.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062406 Title: CVE-2024-32462: Sandbox escape via RequestBackground portal and CWE-88 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/2062406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061009] [NEW] NFS and container connectivity issues
Public bug reported: Using Ubuntu 23.10, gave OpenSnitch 1.5.8.1-1ubuntu0.1 a try which initially looked fine, but then started getting I/O errors apparently due to an NFS server no longer being reachable. Still continued to play with it for a while, including doing a reinstall to see if it changes anything. In that case NFS had no issues, but a Podman container lost network connectivity. Apparently at least the NFS issues are well known and apparently reoccurring at least before a significant change was made: https://github.com/evilsocket/opensnitch/issues/753 https://github.com/evilsocket/opensnitch/issues/510 https://github.com/evilsocket/opensnitch/issues/502 Reporting here because the issue is possibly fixed already upstream by: https://github.com/evilsocket/opensnitch/discussions/942 Expected Ubuntu 24.04 to be the remedy with OpenSnitch 1.6+, but it has the same old version, and if kernel patching is the root of these kind of issues then it's more likely to encounter problems with the updated kernel there. ** Affects: opensnitch (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/2061009 Title: NFS and container connectivity issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensnitch/+bug/2061009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059197] Re: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
Hi Matthew, Its no problem, I can see how changing the version negotiation would be tricky, thanks for looking at it so quickly. Using the workaround and everything working correctly, no dramas Thanks again, Jeffrey -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059197 Title: mount.nfs: Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+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 2059403] [NEW] package bind9-host 1:9.18.18-0ubuntu0.22.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: ubuntu software ubuntu-jammy-main (deb) ProblemType: Package DistroRelease: Ubuntu 22.04 Package: bind9-host 1:9.18.18-0ubuntu0.22.04.2 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 AptOrdering: bind9-libs:amd64: Install gparted-common:amd64: Install gparted:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Mar 28 03:30:55 2024 DuplicateSignature: package:bind9-host:1:9.18.18-0ubuntu0.22.04.2 Setting up gparted-common (1.3.1-1ubuntu1) ... dpkg: error processing package bind9-host (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2024-03-28 (0 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.11 SourcePackage: bind9 Title: package bind9-host 1:9.18.18-0ubuntu0.22.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059403 Title: package bind9-host 1:9.18.18-0ubuntu0.22.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/2059403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059197] [NEW] Issue with nfs4.0 mounts after upgrade to 3.6
Public bug reported: Hello, On Ubuntu Server 20.04.6 LTS with the update of nfs-common package => "nfs-common/focal-updates 1:1.3.4-2.5ubuntu3.5" to "nfs-common/focal- updates 1:1.3.4-2.5ubuntu3.6" I started having issues mounting ntf4.0 volumes. The NFS server supports 4.0, 4.1 and 4.2 The issue appears when using '-t ntfs4' and setting the version using -o vers=. When using 1:1.3.4-2.5ubuntu3.5 I am able to use '-o vers' to set the version when using -t ntfs4 eg mount -t nfs4 -o vers=4.0 -vvv SERVER.local:/srv/data /mnt/test mount.nfs4: trying text-based options 'vers=4.0,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' mount -t nfs4 -o vers=4.1 -vvv SERVER.local:/srv/data /mnt/test mount.nfs4: trying text-based options 'vers=4.1,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' However after upgrading to 1:1.3.4-2.5ubuntu3.6 it always mounts as nfs4.2 mount -t nfs4 -o vers=4.0 -vvv SERVER.local:/srv/data /mnt/test mount.nfs4: trying text-based options 'vers=4.2,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' mount -t nfs4 -o vers=4.1 -vvv SERVER.local:/srv/data /mnt/test mount.nfs4: trying text-based options 'vers=4.2,addr=xx.xx.xx.xx,clientaddr=xx.xx.xx.xx' I would have expected the specified version in -o vers to be used when using '-t nfs4' When using '-t nfs' I am able to mount volumes as nfs 4.0. I understand that 1:1.3.4-2.5ubuntu3.6 fixes version negotiation so maybe this isn't a bug and the intent with '-t nfs4' is to always use the highest version. If so please feel free to close the report ** Affects: nfs-utils (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/2059197 Title: Issue with nfs4.0 mounts after upgrade to 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+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
So after we talked on MM, I think maybe you and Simon have been testing
this instead, so for now is do I need to do this?
Thanks
Jeff
On Tue, Mar 19, 2024 at 3:10 PM Sergio Durigan Junior <
2012...@bugs.launchpad.net> wrote:
> Hi Jeff,
>
> Thanks for the offer. Actually there is!
>
> - If you could test Noble and double/triple check that we don't need to
> do anything else there in order to support maxcpus, that'd be great.
> Just use the "ubuntu" machine type and check if QEMU starts correct with
> more than 288 vCPUs.
>
> - Once the Jammy/Mantic SRUs are accepted, we will need to perform a
> verification for both uploads. I can do it my side, but it would be
> very helpful if you could also verify the uploads on your side.
>
> Thanks.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2012763
>
> Title:
> qemu-system-amd64 max cpus is too low for latest processors
>
> Status in lxd package in Ubuntu:
> New
> Status in qemu package in Ubuntu:
> Confirmed
> Status in lxd source package in Jammy:
> New
> Status in qemu source package in Jammy:
> New
> Status in lxd source package in Lunar:
> Invalid
> Status in qemu source package in Lunar:
> Invalid
> Status in lxd source package in Mantic:
> New
> Status in qemu source package in Mantic:
> Confirmed
> Status in lxd source package in Noble:
> New
> Status in qemu source package in Noble:
> Confirmed
>
> Bug description:
> [ Impact ]
>
> QEMU users on Ubuntu Jammy/Mantic who try to spawn a VM with more than
> 288 vCPUs will not be able to do so, because the machine types
> available don't support such scenario. The following error will
> happen:
>
> qemu-system-x86_64: Invalid SMP CPUs 300. The max CPUs supported by
> machine 'pc-q35-jammy' is 288
>
> [ Test Plan ]
>
> Ideally, the test should be performed in a machine with more than 288
> physical CPUs available. However, due to the difficulty in finding
> such systems, it is possible to emulate the usage of more than 288
> vCPUs.
>
> On a Jammy/Mantic machine, making sure to adjust the machine type
> accordingly, you can do:
>
> $ sudo qemu-system-x86_64 -M pc-q35-jammy,accel=kvm,kernel-
> irqchip=split -device intel-iommu,intremap=on -smp
> cpus=300,maxcpus=300 -enable-kvm -net none -m 4096M -nographic -kernel
> /boot/vmlinuz -initrd /boot/initrd.img -chardev stdio,mux=on,id=char0
> -mon chardev=char0,mode=readline -serial chardev:char0 -append
> "console=ttyS0"
>
> You will notice that the command will fail, as expected.
>
> The proposed fix is to create a new machine type on Jammy/Mantic, in
> order to minimize the possibility of regressions in deployments using
> the existing machine types. This new type is named
> pc-{q35,i440fx}-{jammy,mantic}-maxcpus. When doing the test, make
> sure to provide this new machine type (as part of the "-M" argument).
>
> [ Where problems could occur ]
>
> As explained above, a new machine type was created in order to
> minimize the possibility of regressions. As such, the existing
> "pc-{q35,i440fx}-{jammy,mantic}" machine types should continue to work
> as before, without any change.
>
> [ Original Description ]
>
> During testing of an AMD Genoa CPU, it was discovered that qemu-
> system-amd64 doesn't support enough cpus.
>
> The specific error the tester received was:
>
> qemu-system-x86_64: Invalid SMP CPUs 384. The max supported by machine
> 'pc-q35-7.1' is 288
>
> Looking at the sournce that seems to be an easy fix at first glance:
>
> https://github.com/qemu/qemu/blob/master/hw/i386/pc_q35.c
> 372machine_class_allow_dynamic_sysbus_dev(m, TYPE_VMBUS_BRIDGE);
> 373m->max_cpus = 288;
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/2012763/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=lxd; component=universe;
> status=New; importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=qemu; component=main;
> status=Confirmed; importance=Critical; assignee=
> sergio.duri...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=jammy; sourcepackage=lxd;
> component=None; status=New; importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; distroseries=jammy;
> sourcepackage=qemu; component=main; status=New; importance=Undecided;
> assignee=sergio.duri...@canonical.com;
> Launchpad-Bug: distribution=ubuntu;
[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 2055418] Re: autoinstall crashing on 24.04 desktop daily build
contents of /var/crash attached ** Attachment added: "crash.tgz" https://bugs.launchpad.net/subiquity/+bug/2055418/+attachment/5752934/+files/crash.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055418] Re: autoinstall crashing on 24.04 desktop daily build
@crish it doesn't appear to like that command: $ sudo apport-cli -u 2055418 -c /var/crash/*.crash Usage: apport-cli [options] [symptom|pid|package|program path|.apport/.crash file] apport-cli: error: -u/--update-bug option cannot be used together with options for a new report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055418 Title: autoinstall crashing on 24.04 desktop daily build To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055418/+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 1971619] Re: forward mode open is adding libvirt iptables rules
For the record I was sure to clear (and check they were gone) all libvirt rules between tests using iptables-restore -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971619 Title: forward mode open is adding libvirt iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1971619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971619] Re: forward mode open is adding libvirt iptables rules
Thank you for checking! It seems I will need to retest versions, i was simply checking if it added ANY libvirt rules (iptables-save|grep -i virt), as we expected "open" to NOT add any firewall rules. I was not checking for specific libvirt rules. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971619 Title: forward mode open is adding libvirt iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1971619/+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 1971619] Re: forward mode open is adding libvirt iptables rules
Thank you for the reply. I am certain that I removed the rules between each test. I agree that it could be a different package, I better go through my dpkg log and figure out whats going on here. Is there any way somebody could confirm that they do not see this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971619 Title: forward mode open is adding libvirt iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1971619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1972005] [NEW] Unable to save or attach email attachments since upgrading to 22.04 from 20.04
Public bug reported: This bug reporting process is very cumbersome. I tried using the update- bug application but none of the available options were relevant. If I selected other, I was forced to select a package. How am I supposed to know what package the bug is in? So I just picked one so I could get by this nonsensical barrier. As for the bug I am trying to report: since upgrading to 22.04 last week from 20.04, I have been unable to save attachments to my local disk from Gmail in Chrome or Firefox. Everything appears to work however the file is never actually saved to the file system. Also, when I drag files from the Files app to the browser, either to upload to Jira or attach to Gmail, it appears to work but the attachment is never actually uploaded. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-desktop 1.481 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri May 6 11:26:07 2022 InstallationDate: Installed on 2021-07-31 (279 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to jammy on 2022-04-25 (11 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1972005 Title: Unable to save or attach email attachments since upgrading to 22.04 from 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1972005/+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 1971619] Re: forward mode open is adding libvirt iptables rules
It seems to be present all the way back to 6.0.0-0ubuntu2 which isas far as i could find in an old changelog... is it possible im not rolling the proper packages back? I have been rolling back these debs: libvirt0_6.0.0-0ubuntu2_amd64.deb libvirt-daemon-driver-qemu_6.0.0-0ubuntu2_amd64.deb libvirt-daemon-system-systemd_6.0.0-0ubuntu2_amd64.deb libvirt-clients_6.0.0-0ubuntu2_amd64.deb libvirt-daemon-driver-storage-rbd_6.0.0-0ubuntu2_amd64.deb libvirt-dev_6.0.0-0ubuntu2_amd64.deb libvirt-daemon_6.0.0-0ubuntu2_amd64.deb libvirt-daemon-system_6.0.0-0ubuntu2_amd64.deb (staging) root@server:~$ iptables-save|grep -i virt (staging) root@server:~$ service libvirtd restart (staging) root@server:~$ iptables-save|grep -i virt :LIBVIRT_FWI - [0:0] :LIBVIRT_FWO - [0:0] :LIBVIRT_FWX - [0:0] :LIBVIRT_INP - [0:0] :LIBVIRT_OUT - [0:0] -A INPUT -j LIBVIRT_INP -A FORWARD -j LIBVIRT_FWX -A FORWARD -j LIBVIRT_FWI -A FORWARD -j LIBVIRT_FWO -A OUTPUT -j LIBVIRT_OUT -A LIBVIRT_FWI -o virbr0 -j REJECT --reject-with icmp-port-unreachable -A LIBVIRT_FWO -i virbr0 -j REJECT --reject-with icmp-port-unreachable -A LIBVIRT_FWX -i virbr0 -o virbr0 -j ACCEPT -A LIBVIRT_INP -i virbr0 -p udp -m udp --dport 53 -j ACCEPT -A LIBVIRT_INP -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT -A LIBVIRT_INP -i virbr0 -p udp -m udp --dport 67 -j ACCEPT -A LIBVIRT_INP -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT -A LIBVIRT_OUT -o virbr0 -p udp -m udp --dport 53 -j ACCEPT -A LIBVIRT_OUT -o virbr0 -p tcp -m tcp --dport 53 -j ACCEPT -A LIBVIRT_OUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT -A LIBVIRT_OUT -o virbr0 -p tcp -m tcp --dport 68 -j ACCEPT :LIBVIRT_PRT - [0:0] -A POSTROUTING -j LIBVIRT_PRT :LIBVIRT_PRT - [0:0] -A POSTROUTING -j LIBVIRT_PRT -A LIBVIRT_PRT -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill (staging) root@server:~$ iptables-restore < /etc/iptables/rules.v4 (staging) root@server:~$ dpkg -l | grep libvirt ii libvirt-clients 6.0.0-0ubuntu2 amd64Programs for the libvirt library ii libvirt-daemon6.0.0-0ubuntu2 amd64Virtualization daemon ii libvirt-daemon-driver-qemu6.0.0-0ubuntu2 amd64Virtualization daemon QEMU connection driver ii libvirt-daemon-driver-storage-rbd 6.0.0-0ubuntu2 amd64Virtualization daemon RBD storage driver ii libvirt-daemon-system 6.0.0-0ubuntu2 amd64Libvirt daemon configuration files ii libvirt-daemon-system-systemd 6.0.0-0ubuntu2 amd64Libvirt daemon configuration files (systemd) ii libvirt-dev:amd64 6.0.0-0ubuntu2 amd64development files for the libvirt library ii libvirt-glib-1.0-0:amd64 3.0.0-1 amd64libvirt GLib and GObject mapping library ii libvirt0:amd646.0.0-0ubuntu2 amd64library for interfacing with different virtualization systems ii python3-libvirt 6.1.0-1 amd64libvirt Python 3 bindings (staging) root@server:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971619 Title: forward mode open is adding libvirt iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1971619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971619] Re: forward mode open is adding libvirt iptables rules
I found it was 6.0.0-0ubuntu8 and I am triggering the bug even while that version is installed, which feels wrong... How would I be the first to notice this after 2 years? it seems unlikely, but here we are -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971619 Title: forward mode open is adding libvirt iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1971619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971619] Re: forward mode open is adding libvirt iptables rules
Thank you for the instructions on how to test old versions. I was wrong above when i said it was not present in 8.8, indeed it was but I had not noticed it until more recently. I have tested back to 8.1 and I confirm it was there as well. I am unable to get/test 8.0 and i do not know what the version before that is. $ pull-lp-debs libvirt 6.0.0-0ubuntu8.0 Source package lookup failed, trying lookup of binary package libvirt The binary package 'libvirt' version 6.0.0-0ubuntu8.0 does not exist in the Ubuntu primary archive for architecture amd64 The source package 'libvirt' version 6.0.0-0ubuntu8.0 does not exist in the Ubuntu primary archive Can I help more? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971619 Title: forward mode open is adding libvirt iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1971619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971619] Re: forward mode open is adding libvirt iptables rules
This bug definitely did not exist in 6.0.0-0ubuntu8.8 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971619 Title: forward mode open is adding libvirt iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1971619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971619] Re: forward mode open is adding libvirt iptables rules
I was able to confirm this bug exists in 6.0.0-0ubuntu8.15 as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971619 Title: forward mode open is adding libvirt iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1971619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971619] Re: forward mode open is adding libvirt iptables rules
I also filed this bug directly with the libvirt team at: https://gitlab.com/libvirt/libvirt/-/issues/307 ** Bug watch added: gitlab.com/libvirt/libvirt/-/issues #307 https://gitlab.com/libvirt/libvirt/-/issues/307 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971619 Title: forward mode open is adding libvirt iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1971619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971619] [NEW] forward mode open is adding libvirt iptables rules
Public bug reported: After "auto security updates" updated my libvirt I have noticed that forward mode open is adding LIBVIRT rules to my iptables for the default network. This was supposed to happen with forward mode nat, but not with forward mode open. apt-cache policy libvirt-daemon: libvirt-daemon: Installed: 6.0.0-0ubuntu8.16 Candidate: 6.0.0-0ubuntu8.16 Version table: *** 6.0.0-0ubuntu8.16 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 6.0.0-0ubuntu8 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages lsb_release -rd: Description:Ubuntu 20.04.3 LTS Release:20.04 VM network settings: virsh net-dumpxml --inactive default default 17c58686-736c-49e4-8ae9-99a8d25f032c What I expect to happen: Because I have forward mode='open' I expect that when libvirtd gets restarted that it will NOT load its own rules into my firewall. This has been the case for me since mode open was added. What is happening: (staging) root@server:~$ iptables-save|grep -i virt (staging) root@server:~$ service libvirtd restart (staging) root@server:~$ iptables-save|grep -i virt :LIBVIRT_PRT - [0:0] -A POSTROUTING -j LIBVIRT_PRT -A LIBVIRT_PRT -o virbr0 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill :LIBVIRT_PRT - [0:0] -A POSTROUTING -j LIBVIRT_PRT -A LIBVIRT_PRT -s 192.168.122.0/24 -d 224.0.0.0/24 -j RETURN -A LIBVIRT_PRT -s 192.168.122.0/24 -d 255.255.255.255/32 -j RETURN -A LIBVIRT_PRT -s 192.168.122.0/24 ! -d 192.168.122.0/24 -p tcp -j MASQUERADE --to-ports 1024-65535 -A LIBVIRT_PRT -s 192.168.122.0/24 ! -d 192.168.122.0/24 -p udp -j MASQUERADE --to-ports 1024-65535 -A LIBVIRT_PRT -s 192.168.122.0/24 ! -d 192.168.122.0/24 -j MASQUERADE :LIBVIRT_FWI - [0:0] :LIBVIRT_FWO - [0:0] :LIBVIRT_FWX - [0:0] :LIBVIRT_INP - [0:0] :LIBVIRT_OUT - [0:0] -A INPUT -j LIBVIRT_INP -A FORWARD -j LIBVIRT_FWX -A FORWARD -j LIBVIRT_FWI -A FORWARD -j LIBVIRT_FWO -A OUTPUT -j LIBVIRT_OUT -A LIBVIRT_FWI -d 192.168.122.0/24 -o virbr0 -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A LIBVIRT_FWI -o virbr0 -j REJECT --reject-with icmp-port-unreachable -A LIBVIRT_FWO -s 192.168.122.0/24 -i virbr0 -j ACCEPT -A LIBVIRT_FWO -i virbr0 -j REJECT --reject-with icmp-port-unreachable -A LIBVIRT_FWX -i virbr0 -o virbr0 -j ACCEPT -A LIBVIRT_INP -i virbr0 -p udp -m udp --dport 53 -j ACCEPT -A LIBVIRT_INP -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT -A LIBVIRT_INP -i virbr0 -p udp -m udp --dport 67 -j ACCEPT -A LIBVIRT_INP -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT -A LIBVIRT_OUT -o virbr0 -p udp -m udp --dport 53 -j ACCEPT -A LIBVIRT_OUT -o virbr0 -p tcp -m tcp --dport 53 -j ACCEPT -A LIBVIRT_OUT -o virbr0 -p udp -m udp --dport 68 -j ACCEPT -A LIBVIRT_OUT -o virbr0 -p tcp -m tcp --dport 68 -j ACCEPT ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: firewall libvirt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971619 Title: forward mode open is adding libvirt iptables rules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1971619/+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 1970076] Re: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade
I can confirm that the issue may be in qemu in 22.04. A "real" s390x running 22.04 does not have this issue and the same installation image does not have this issue running on Windows 11, qemu version 7.0.0. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970076 Title: "User process fault: interruption code 0011 ilc:3" on SSH client/server upon Jammy upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1970076/+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 1969656] [NEW] package linux-image-5.4.0-109-generic 5.4.0-109.123 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Not sure ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-109-generic 5.4.0-109.123 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed Apr 20 09:53:29 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. Lspci: Lspci-vt: -[:00]- Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-39-generic root=PARTUUID=3e5a9664-db4e-4d98-b48a-7cc19a4e843b ro quiet splash video=hyperv_fb:1366x768 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.15 RfKill: SourcePackage: initramfs-tools Title: package linux-image-5.4.0-109-generic 5.4.0-109.123 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2019 dmi.bios.release: 4.0 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 3713-0728-9815-5000-5213-4336-15 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969656 Title: package linux-image-5.4.0-109-generic 5.4.0-109.123 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1969656/+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 1965219] Re: gnome lock screen does not permit reentering password
It's seemingly much less bad if I disable suspend when plugged into power, and maybe the remaining problems come from plugging in power before resume. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+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 1965219] Re: gnome lock screen does not permit reentering password
This one seemed like it refused to wake even enough to draw a black scree, just stayed asleep. I've no idea if this is hlepful ** Attachment added: "refuses_to_wake.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5579458/+files/refuses_to_wake.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+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 1965219] Re: gnome lock screen does not permit reentering password
Another purple screen lockup. It's now also more common the system runs how while closed. ** Attachment added: "purple_screen_lockup-8_april.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5578017/+files/purple_screen_lockup-8_april.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965219] Re: gnome lock screen does not permit reentering password
I've still not tried other kernels, in part because ubuntu keeps pushing out new OEM kernels, so I give them all a try, but the same basic problem persist, either gnome-shell gives only a black screen, or else the whole system hangs on the purple screen. I've far more diverse crashes with the latest kernels and the bolt upgrade: https://errors.ubuntu.com/user/f1e063bb5e8c4439fa13d51f06f02ce6ad03d098946e7597fd170a17325d98a76475f94a90f27677619cb85b6c0bd1cc406eece2601001754138f20d7209c37a -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965219 Title: gnome lock screen does not permit reentering password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+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
