Based on discussions at https://github.com/nfs-ganesha/nfs-
ganesha/issues/1123, it seems this is something released with nfs-
ganesha V4, so IIUC, this is something that will only be available to an
Openstack + Manila + Ceph + NFS Ganesha in Noble Numbat, since it offers
nfs-ganesha 4.3-8ubuntu1
This is also being discussed upstream: https://github.com/nfs-
ganesha/nfs-ganesha/issues/1123
** Bug watch added: github.com/nfs-ganesha/nfs-ganesha/issues #1123
https://github.com/nfs-ganesha/nfs-ganesha/issues/1123
--
You received this bug notification because you are a member of Ubuntu
Hi Peter,
The NFS client is a Jammy VM running nfs-common 1:2.6.1-1ubuntu1.2 and
kernel 5.15.0-102-generic.
I'm running a sosreport and will attach it here soon.
Regards,
Fabio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "sosreport-jammy-130612-2024-05-22-dnjwtoi.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/nfs-ganesha/+bug/2064657/+attachment/5781410/+files/sosreport-jammy-130612-2024-05-22-dnjwtoi.tar.xz
--
You received this bug notification because you are a member of Ubuntu
** Tags added: rls-ff-incoming rls-jj-incoming rls-mm-incoming rls-nn-
incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054343
Title:
arm64 build of gcc-10 10.5.0-3ubuntu1 still broken
It seems 0.142ubuntu19 would be exposed to the bug. To test whether or
not my use case would be affected by it, I've booted a Jammy instance
with initramfs-tools 0.142ubuntu19, and I can't hit the problem. It is
booting well through iscsi. My cmdline is as below, so it might not be
exposed to the
It seems 0.142ubuntu19 would be exposed to the bug. To test whether or
not my use case would be affected by it, I've booted a Jammy instance
with initramfs-tools 0.142ubuntu19, and I can't hit the problem. It is
booting well through iscsi. My cmdline is as below, so it might not be
exposed to the
Public bug reported:
When booting a Noble Numbat (Ubuntu 24.04) instance on Oracle Cloud,
clout-init ends up in a degraded state reporting "Invalid network-config
provided". Details are displayed below:
ubuntu@fabio-noble-baremetal-benjaminfix:~$ sudo cloud-init status -l
status: done
** Attachment added: "cloud-init.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2056460/+attachment/5753817/+files/cloud-init.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've tested launching a Oracle Cloud baremetal instance (which boots
from iSCSI) using such patch, and all worked well:
https://pastebin.ubuntu.com/p/3cdFdYBVFG/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've tested launching a Oracle Cloud baremetal instance (which boots
from iSCSI) using such patch, and all worked well:
https://pastebin.ubuntu.com/p/3cdFdYBVFG/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I've tested the patch and it fixes the issue. I can confirm the MTU
settings are now correct and curl works fine. I also confirmed it
allowed cloud-init to run and fully complete the boot process:
https://pastebin.ubuntu.com/p/KfcP7wmjjV/
There are no cloud-init errors:
I've tested the patch and it fixes the issue. I can confirm the MTU
settings are now correct and curl works fine. I also confirmed it
allowed cloud-init to run and fully complete the boot process:
https://pastebin.ubuntu.com/p/KfcP7wmjjV/
There are no cloud-init errors:
Between initramfs-tools 0.142ubuntu8 and 0.142ubuntu9, we've Replaced
dhclient by dhcpcd (LP: #2024164).
When a DHCP server provides MTU settings to dhcpcd, it configures the
routes with the appropriate mtu value (due to "option interface_mtu" in
/etc/dhcpcd.conf), but it does not configure the
Sorry for the late feedback, but sharing here:
AWS docs regarding best practices regarding cpu-starvation [1] do not
recommend disabling the irqbalance service. Quoting the doc:
> "Note: we do not recommend disabling irqbalance service. ENA driver
doesn’t provide affinity hints, and if device
Sorry for the late feedback, but sharing here:
AWS docs regarding best practices regarding cpu-starvation [1] do not
recommend disabling the irqbalance service. Quoting the doc:
> "Note: we do not recommend disabling irqbalance service. ENA driver
doesn’t provide affinity hints, and if device
Public bug reported:
In an environment where /etc/krb5.conf sets "default_ccache_name =
FILE:/tmp/krb5cc_%{uid}" and you don't have the KRB5CCNAME variable set,
running "adsysctl update" with a AD domain user will fail.
If you either export the variable with the path to the kerberos ticket
OR
For item 1:
* Confirm that makedumpfile works as expected by triggering a kdump.
I can confirm that makedumpfile 1:1.6.7-1ubuntu2.5 from focal-
proposed/main worked well when I triggered a dump in a system:
ubuntu@fabio-small-makedumpfile:~$ sudo hostnamectl
Static hostname:
For item 2:
* Confirm that the patched makedumpfile works as expected on a system
known to experience the issue.
Unfortunately I'm no longer able to reproduce the original issue.
Even running on the same hardware where this was originally noticed,
with the same kernel version
Hi Chris,
You're correct, I'm sorry. My test on comment #23 is the 3rd item you
listed.
Let me work on 1 and 2 and I'll get back here.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
I've tested makedumpfile from -proposed on Focal and it looks good to
me.
Using a vmcore file with 2TB as an input:
- Original makedumpfile 1.6.7-1ubuntu2.4 fails:
ubuntu@kdump-instance:~$ sudo apt-cache policy makedumpfile
makedumpfile:
Installed: 1:1.6.7-1ubuntu2.4
Candidate:
Hi Nafees, I discussed this with Mitchell and we are still looking into
the best possible way to move forward with this SRU. We'll keep this bug
update as soon as we have some more details to share.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I've tested this in Lunar and Mantic.
TL;DR: In Lunar I hit the exact same issue as in Kinetic. After
installing adsys, I'm no longer able to login using a domain user. On
Mantic, it works fine and I'm able to login even after installing adsys.
On the other hand, both Lunar and Mantic have the
Hi Steve,
Would you and the SRU team reconsider the "won't fix" decision or
further elaborate on the regression problem, based on the comment above?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
I just tested Ubuntu 22.04 and I can confirm it fixes the issue.
First, used 22.04 with the current mutter version available in jammy-
updates:
user1@U-20CG3JVH1ALS3:~$ sudo apt-cache policy mutter-common libmutter-10-0
gir1.2-mutter-10
[sudo] password for user1:
mutter-common:
Installed:
I just tested Ubuntu 22.04 and I can confirm it fixes the issue.
First, used 22.04 with the current mutter version available in jammy-
updates:
user1@U-20CG3JVH1ALS3:~$ sudo apt-cache policy mutter-common libmutter-10-0
gir1.2-mutter-10
[sudo] password for user1:
mutter-common:
Installed:
Another suggestion from one of our Engineers is that you can also set it
inside your python script, something like this:
```
from setuptools import setup, Extension
import sysconfig
extra_flags=sysconfig.get_config_var('CFLAGS').split()
setup(
name="test",
Alright, thanks for the information @Steve.
Hi @Nafees,
With the information above, it seems there's a regression risk if we fix
this bug in python2.7 in Focal, and the risk outstands the benefits of
the fix, as it seems to be an uncommon use-case and there's a workaround
for it, so we wouldn't
Hi,
Thank you for the package in -proposed.
I just tested Ubuntu 22.04 and I can confirm it fixes the issue.
First, used 22.04 with the current mutter version available in jammy-
updates:
user0@U-2RVWD6LKXR3GE:~$ sudo apt-cache policy mutter-common libmutter-10-0
gir1.2-mutter-10
Hi,
Thank you for the package in -proposed.
I just tested Ubuntu 22.04 and I can confirm it fixes the issue.
First, used 22.04 with the current mutter version available in jammy-
updates:
user0@U-2RVWD6LKXR3GE:~$ sudo apt-cache policy mutter-common libmutter-10-0
gir1.2-mutter-10
It's also worth mentioning that, a patch was backported mentioning "#
DP: Allow setting BASECFLAGS, OPT and EXTRA_LDFLAGS (like, CC, CXX, CPP,
CFLAGS, CPPFLAGS, CCSHARED, LDSHARED) from the environment." [1], but
then OPT is not being added at all by the patch (which had just
mentioned adding it),
Hi Steve,
Thanks for looking into this SRU request.
Their original request was specifically to python2.7 on Ĵammy, which
matches your comment on the eligible releases.
The request is not to rebuild the python extensions, but to fix the
compiler so new modules getting compiled will inherit the
OK, thanks for the information. The one I had tested was 42.9-0ubuntu2
with Jammy. I'll test again when 42.9-0ubuntu3 is available in
-proposed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
OK, thanks for the information. The one I had tested was 42.9-0ubuntu2
with Jammy. I'll test again when 42.9-0ubuntu3 is available in
-proposed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
I've tested the mutter packages from -proposed in an AWS Workspace:
https://pastebin.ubuntu.com/p/9Yvgfs7yZr/
And I'm able to successfully change the scale to 200% and then revert
the setting.
The following messages are logged when changing to 200%:
https://pastebin.ubuntu.com/p/Y5QdXSqcsW/
I've tested the mutter packages from -proposed in an AWS Workspace:
https://pastebin.ubuntu.com/p/9Yvgfs7yZr/
And I'm able to successfully change the scale to 200% and then revert
the setting.
The following messages are logged when changing to 200%:
https://pastebin.ubuntu.com/p/Y5QdXSqcsW/
I've tested Focal and it works well with adsys from -proposed:
https://pastebin.ubuntu.com/p/6RBcBpZq2T/
And also does Jammy:
https://pastebin.ubuntu.com/p/pqvgSkkmcQ/
I'm having issues with Kinetic. When I install adsys, I'm no longer able
to login to the instance, I'm getting the following
For completeness: re: the Lunar issue that I mentioned in comment #22
and that Andreas suggested me to file a separate bug (on comment #28):
I tested a freshly installed Lunar VM, and also did 'apt upgrade'
everything in my previous Lunar VM (where I was originally hitting the
problem I
Thank you very much for the great job narrowing this, Daniel!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782
Title:
Xdcv: Changing display scale setting and reverting it fails
Thank you very much for the great job narrowing this, Daniel!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2020782
Title:
Xdcv: Changing display scale setting and reverting it
Hi Nafees,
I've discussed this case with our Engineering team and they are working
on the SRU process to get this fix released, however this should take
around 1 month before it gets published to -updates. Although we are
prioritizing it, the fix still needs to go to the -proposed repository
for
Daniel,
Regarding 3 (the blank screen issue when enabling a monitor): I can
confirm that the issue happens when you're using Workspaces client
5.9.0.4129 (Windows client version) and no longer happens (even with
Xdcv + Gnome) in 5.10.0.4196.
And, by checking the client release notes [1]:
Daniel,
Regarding 3 (the blank screen issue when enabling a monitor): I can
confirm that the issue happens when you're using Workspaces client
5.9.0.4129 (Windows client version) and no longer happens (even with
Xdcv + Gnome) in 5.10.0.4196.
And, by checking the client release notes [1]:
Ignacio, if Xdcv ever wants to support Fractional Scaling, I believe you
will also need to look at the details shared by Daniel in his comment
#16. Otherwise, even if we fix the zero hz issue, you will be able to
change/revert scale, but will also need to make sure fractional scaling
is disabled.
Ignacio, if Xdcv ever wants to support Fractional Scaling, I believe you
will also need to look at the details shared by Daniel in his comment
#16. Otherwise, even if we fix the zero hz issue, you will be able to
change/revert scale, but will also need to make sure fractional scaling
is disabled.
Daniel,
A few items to make sure I'm on the same page:
1. So, IIUC, you're saying that the "final fix" should be the vv5
package, which contains the fix to the zero hz bug (loosening mutter to
accept zero-Hz, as this is the bogus refresh rate being reported by
Xdcv) + the caveat for AWS to
Daniel,
A few items to make sure I'm on the same page:
1. So, IIUC, you're saying that the "final fix" should be the vv5
package, which contains the fix to the zero hz bug (loosening mutter to
accept zero-Hz, as this is the bogus refresh rate being reported by
Xdcv) + the caveat for AWS to
Verified a Focal guest as follows:
1. Reproduced the problem with kernel 5.4.0-152-generic:
https://pastebin.ubuntu.com/p/Cgj6j4Prbc/
2. As a workaround removed:
0x0003
3. Installed kernel from -proposed:
root@ubuntu:~# apt-cache policy linux-image-virtual linux-virtual
I've verified a Jammy guest as follows:
1. Reproduced the problem with kernel 5.15.0-75-generic:
https://pastebin.ubuntu.com/p/844W5SzjR8/
2. As a workaround removed:
0x0003
3. Installed kernel from -proposed:
root@ubuntu:~# apt-cache policy linux-image-virtual linux-virtual
Hi Daniel,
Thanks again, and I totally agree that we need to focus on the revert
resolution issue in this LP bug. I wasn't willing to discuss the other
issues here, but to summarize my understanding so far, so as to make
sure we are on the same page.
Also, I tested "xrandr --output VNC-output-1
Hi Daniel,
Thanks again, and I totally agree that we need to focus on the revert
resolution issue in this LP bug. I wasn't willing to discuss the other
issues here, but to summarize my understanding so far, so as to make
sure we are on the same page.
Also, I tested "xrandr --output VNC-output-1
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/2020641
Title:
Installing or removing apps through snap-store
> Try logging into a non-GNOME Xorg session on Workspaces
> if you can. Then use the 'xrandr' command to set a mode
> to turn on one of the unused virtual monitors. If that
> causes the DCV client to go blank then we have proven
> it's not mutter's fault.
I did test that with a Cinnamon session
> Try logging into a non-GNOME Xorg session on Workspaces
> if you can. Then use the 'xrandr' command to set a mode
> to turn on one of the unused virtual monitors. If that
> causes the DCV client to go blank then we have proven
> it's not mutter's fault.
I did test that with a Cinnamon session
Although Mustafa says he's not well-versed, he's way smarter than me :)
So his comment#26 seems to be much more relevant than what I have to
say, but I'd like to reply to Daniel's comment#24/25 anyway:
I saw the details you mentioned on comment #16, and I also have
fractional scaling turned off.
Although Mustafa says he's not well-versed, he's way smarter than me :)
So his comment#26 seems to be much more relevant than what I have to
say, but I'd like to reply to Daniel's comment#24/25 anyway:
I saw the details you mentioned on comment #16, and I also have
fractional scaling turned off.
Daniel,
For when you have a chance, we've discussed this bug a bit in #ubuntu-
release in Libera.Chat. The SRU team would like to hear your opinion on
SRU'ing this fix for lunar, and your comments above on mentioning that
it's unlikely to be useful vs. what you mentioned previously of this
being
Hi Daniel,
Thanks again.
Tested 42.5-0ubuntu1vv5
When I apply the 200% scale:
https://pastebin.ubuntu.com/p/MfS9vpT6KB/
When I revert it:
https://pastebin.ubuntu.com/p/SHtvrXyPkY/
And then I get this situation (possibly due to what you mentioned on the
settings app attempting to enable the
Hi Daniel,
Thanks again.
Tested 42.5-0ubuntu1vv5
When I apply the 200% scale:
https://pastebin.ubuntu.com/p/MfS9vpT6KB/
When I revert it:
https://pastebin.ubuntu.com/p/SHtvrXyPkY/
And then I get this situation (possibly due to what you mentioned on the
settings app attempting to enable the
Daniel,
Thanks for chiming in.
I've tried reproducing this bug outside of DCV, but no lucky.
What I tried last is to launch a baremetal instance on AWS (g4dn.metal)
with the same Nvidia GPUs as the instance type where we are consistently
able to reproduce this problem, and then I:
1. Installed
I was getting some inconsistent and confusing results on my tests, so I
decided to start from scratch with a fresh VM (qemu) and also a fresh
Workspace (AWS).
In a freshly installed Jammy VM (on qemu, not AWS), out of the box we
have factional scaling disabled, so I tried changing scale to 200%
I was getting some inconsistent and confusing results on my tests, so I
decided to start from scratch with a fresh VM (qemu) and also a fresh
Workspace (AWS).
In a freshly installed Jammy VM (on qemu, not AWS), out of the box we
have factional scaling disabled, so I tried changing scale to 200%
I'm not sure how can we verify lunar. There's no DCV available for non-
LTS releases, and there's no known way of reproducing this issue without
DCV.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Hi Andreas,
I'm sorry, I missed your request for the additional tests. Just did them
for Jammy. Adding here:
- Logged in as ubuntu user and launched Firefox, LibreOffice and gedit:
https://pastebin.ubuntu.com/p/H3WVmVkgJh/
- Switched user to fabiomirmar and opened Thunderbird, skype and
Hi,
I've been able to verify that the package in -proposed fixes the issue
for Jammy:
Before applying the patch we have:
https://pastebin.ubuntu.com/p/KphZJjZRsb/
when attempting a "sudo snap disconnect skype:opengl :opengl" we can see
the gdm session being launched:
Thanks for the investigation Daniel.
Indeed my inability to change the scale with the first patch was due to
low resolution in my client machine.
Interesting enough, I tried reproducing this in a Local VM with Xdcv
(with just regular mutter packages, straight from our archives, no PPA),
and I'm
Thanks for the investigation Daniel.
Indeed my inability to change the scale with the first patch was due to
low resolution in my client machine.
Interesting enough, I tried reproducing this in a Local VM with Xdcv
(with just regular mutter packages, straight from our archives, no PPA),
and I'm
I also tested Daniel's mutter package with:
sudo add-apt-repository ppa:vanvugt/mutter
sudo apt update
sudo apt upgrade
And rebooted the Workspace just in case.
I know Mustafa mentioned he was still able to reproduce the issue. In my
case, I wasn't but on the other hand, I can't do the action
I also tested Daniel's mutter package with:
sudo add-apt-repository ppa:vanvugt/mutter
sudo apt update
sudo apt upgrade
And rebooted the Workspace just in case.
I know Mustafa mentioned he was still able to reproduce the issue. In my
case, I wasn't but on the other hand, I can't do the action
Hi Daniel,
I'm not with the SEG team and I would need assistance from someone
building that and providing the debs or a ppa. I've also subscribed
Mustafa, from SEG, to this bug, as he's assisting me investigating this
issue.
Regards,
Fabio Martins
--
You received this bug notification because
Hi Daniel,
I'm not with the SEG team and I would need assistance from someone
building that and providing the debs or a ppa. I've also subscribed
Mustafa, from SEG, to this bug, as he's assisting me investigating this
issue.
Regards,
Fabio Martins
--
You received this bug notification because
Also tested with mutter-common 42.5-0ubuntu1 and gnome-shell
42.5-0ubuntu1:
fabiomirmar@U-1JSKZM4R9U78P:~$ sudo apt-cache policy mutter-common
[sudo] password for fabiomirmar:
mutter-common:
Installed: 42.5-0ubuntu1
Candidate: 42.5-0ubuntu1
Version table:
*** 42.5-0ubuntu1 500
Also tested with mutter-common 42.5-0ubuntu1 and gnome-shell
42.5-0ubuntu1:
fabiomirmar@U-1JSKZM4R9U78P:~$ sudo apt-cache policy mutter-common
[sudo] password for fabiomirmar:
mutter-common:
Installed: 42.5-0ubuntu1
Candidate: 42.5-0ubuntu1
Version table:
*** 42.5-0ubuntu1 500
Public bug reported:
In Amazon Workspaces running Ubuntu 22.04, when attempting to change the
Scale in the Gnome Display settings, if you click on a different scale
(i.e. changing from 100% to 200%) and hitting apply, it will bring up a
prompt asking if you want to keep or revert the changes and
Public bug reported:
In Amazon Workspaces running Ubuntu 22.04, when attempting to change the
Scale in the Gnome Display settings, if you click on a different scale
(i.e. changing from 100% to 200%) and hitting apply, it will bring up a
prompt asking if you want to keep or revert the changes and
@Daniel,
My understanding is that bug 2019751 is the same as bug 1989170, but
public. Since the fix was not released to Jammy, bug 2019751 aims to
address that (although your question might be targeted to Lunar, since I
see bug 1989170 was released to Kinetic.
--
You received this bug
Thank you Julian and Gerald.
I've verified that upgrading grub-efi-amd64-bin to 2.06-2ubuntu14 (from
-proposed) fixes the issue both in Focal and Jammy.
--
You received this bug notification because you are a member of SE SRU
("STS") Sponsors, which is subscribed to the bug report.
@Nafees,
I'm sorry, I hadn't noticed that the file produced by python3 was
different (and I did have the test.so in my directory because I had
built it with python2 before, so I was just grepping the same file). I
see the problem now and I'm checking it with our Engineering team.
Regards,
Fabio
Hi Nafees,
Thank you for the reproducer and instructions.
Per your comments, I would expect this to work well with python3 on
20.04, however, my tests indicated that python2 and python3 are both
behaving the same way. In the example below, I'm using python3 and I
also don't see the -O2
Hello Nafees,
Can you share this setup.py that we can use to reproduce the problem and
investigate?
Regards,
Fabio Martins
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
I believe this patch might have been dropped for newer linux-aws
kernels. I just reproduced this problem while running 5.15.0-1026-aws
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
CPC has worked on removing /etc/cloud/cloud.cfg.d/99-disable-network-
config.cfg from Oracle images and this is completed started with Images
with build >=20221123
I just used our daily images to create 3 custom images with:
- Jammy: 20221214
- Focal: 20221214
- Bionic: 20221205
And launched
Hi Steve,
I've reproduced the problem with a kinetic VM, and then installed the
grub2 packages from -proposed and I can confirm it fixes this issue:
root@ubuntu:~# free -k
totalusedfree shared buff/cache available
Mem:17428828 215288
This is a grub bug and it is being tracked here:
[SRU] unable to boot guest with large memory when SEV is enabled on host
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1989446
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: grub2 (Ubuntu Impish)
This is a grub bug and it is being tracked here:
[SRU] unable to boot guest with large memory when SEV is enabled on host
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/1989446
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug
Public bug reported:
Feature Request:
When installing a system over the network using live installer
(subiquity), you can use the kernel cmdline option ip= [1] to provide
the network configuration.
In certain situations, it would be ideal to be able to configure a lacp
bond during this process.
Hi Si-Wei, the 5.11 kernel has reached EOL in Feb 2022. Kernel 5.15 is
the one currently being used for linux-oracle kernel on Focal (20.04)
and Jammy (22.04), and it has the commit that you mentioned above:
$ git log --oneline | grep -i "Fix page DMA map/unmap attributes"
a865fe280b96 net/mlx5e:
That is also available in the 5.4 kernel, so that also covers Bionic
(18.04) guests if needed:
$ git log --oneline | grep -i "Fix page DMA map/unmap attributes"
53176ef0d809 net/mlx5e: Fix page DMA map/unmap attributes
$ git tag --contains 53176ef0d809
Ubuntu-oracle-5.4.0-1071.77
Just tested this 5.13.0-1029.32~lp1977919.1 kernel and confirmed that it
fixes the issue (doesn't crash when running the same docker container
that would crash in the -1028 kernel)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws
Hi Brian,
Thanks for that. I've tested and validated that ec2-instance-connect
from jammy-proposed fixes the issue. Here are the evidences:
https://pastebin.ubuntu.com/p/dPD6vyS6g4/
Cheers,
Fabio Martins
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I also tested with mssh to make it works well:
When running ec2-instance-connect 1.1.14-0ubuntu1 (from Jammy) and
trying to connect with mssh:
fabio@fabio-canonical:~/.aws$ mssh ubuntu@i-0af3232b4fb6ed642
ubuntu@3.91.56.142: Permission denied (publickey).
Due to the bug, we can see the key
I've also updated the [Test Plan] section of the bug description
** Description changed:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
+
+ - Check that the ipconfig utility is able to obtain an IP
I've also updated the [Test Plan] section of the bug description
** Description changed:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
+
+ - Check that the ipconfig utility is able to obtain an IP
I've also updated the [Test Plan] section of the bug description
** Description changed:
[Impact]
In some cases, ipconfig can take a longer time than the user-specified
timeouts, causing unexpected delays.
[Test Plan]
+
+ - Check that the ipconfig utility is able to obtain an IP
Hello Robie,
I've validated that the package from -proposed works well, testing in my
VM based environment. I haven't tested it on Oracle bare metal (where
the original issue happened) as that is a type of instance hard to get
access to. Given that the test packages had proven to fix the original
Hello Robie,
I've validated that the package from -proposed works well, testing in my
VM based environment. I haven't tested it on Oracle bare metal (where
the original issue happened) as that is a type of instance hard to get
access to. Given that the test packages had proven to fix the original
Hello Robie,
I've validated that the package from -proposed works well, testing in my
VM based environment. I haven't tested it on Oracle bare metal (where
the original issue happened) as that is a type of instance hard to get
access to. Given that the test packages had proven to fix the original
I've tested the package from -proposed and I can confirm it fixes the
problem:
Installed from -proposed:
root@ubuntu:~# apt-cache policy klibc-utils
klibc-utils:
Installed: 2.0.4-9ubuntu2.2
Candidate: 2.0.4-9ubuntu2.18.04.1
Version table:
2.0.4-9ubuntu2.18.04.1 500
500
I've tested the package from -proposed and I can confirm it fixes the
problem:
Installed from -proposed:
root@ubuntu:~# apt-cache policy klibc-utils
klibc-utils:
Installed: 2.0.4-9ubuntu2.2
Candidate: 2.0.4-9ubuntu2.18.04.1
Version table:
2.0.4-9ubuntu2.18.04.1 500
500
I've tested the package from -proposed and I can confirm it fixes the
problem:
Installed from -proposed:
root@ubuntu:~# apt-cache policy klibc-utils
klibc-utils:
Installed: 2.0.4-9ubuntu2.2
Candidate: 2.0.4-9ubuntu2.18.04.1
Version table:
2.0.4-9ubuntu2.18.04.1 500
500
1 - 100 of 157 matches
Mail list logo
