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
** 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
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
** 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.
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
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.
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
** 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
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
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
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
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
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
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
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
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
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
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
--
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
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 i
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
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
** 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:
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.
@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
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
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
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
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
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
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
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
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
** 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
** 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
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
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
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
** 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
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
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
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
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
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
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,
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:
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
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
** 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
** 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
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:
>
>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
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
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
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
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
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
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
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:
** 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
** 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
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
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
>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
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
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
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
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.
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
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.
**
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.
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.
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.
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
** 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
** 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
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
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
** 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
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.
** 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
** 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.ne
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
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
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
** 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
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]
** 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
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
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
** 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 en
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,
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
** Tags added: servcert-230
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967116
Title:
[Ubuntu 22.04] mpi3mr: Request to include latest bug fixes
To manage notifications about this bug go to:
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966203
Title:
Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966203
Title:
Syslog shows "systemd-udevd[2837]: nvme0n1: Process ... failed with
Can this be reproduced in EFI mode, or is it only when in Legacy Mode?
ALso, what is the mount command you are using? Just basic like "mount
/dev/device /mountpoint"? Or is there a different mount command you are
using that is failing?
--
You received this bug notification because you are a
It's growing kinda worst with 5.14.0-1031-oem in that gnome-shell now
more reliably fails unsleep, but I've not yet seen any real crash under
5.14.0-1031-oem.
I've still not tried non OWM kernels.
** Attachment added: "black_screen_with_mouse-29_march-b.txt"
** Tags added: soa
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966194
Title:
[Jammy, mlx5, ConnectX-7] add CX7 support for software steering
To manage notifications about this bug go to:
** Description changed:
SRU Justification:
[IMPACT]
This is being reported by a hardware partner as it is being noticed a
lot both in their internal testing teams and also being reported with
some frequency by customers who are seeing these messages in their logs
and thus it is
1 - 100 of 8792 matches
Mail list logo
