Hi Pramod,
I downloaded the driver version you listed, 550.90.07 from the NVIDIA
website:
https://www.nvidia.com/download/driverResults.aspx/226768/en-us/
This gave me NVIDIA-Linux-x86_64-550.90.07.run.
I managed to successfully install this to 6.8.0-31-generic, and 6.8.0-35-generic
without any
Performing verification for Focal.
I started a fresh focal VM, and installed irqtop 2.4-2ubuntu0.5 and
ruby-curses 1.2.4-1build1 from -updates.
I then started irqtop:
$ sudo irqtop
/usr/bin/irqtop:598: warning: rb_safe_level will be removed in Ruby 3.0
Performing verification for Jammy.
I started a fresh jammy VM, and installed irqtop 2.6-2ubuntu3 with ruby-
curses 1.2.4-1build3, from -updates.
I then ran:
$ sudo irqtop
:85:in
`require': /usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0/curses.so:
undefined symbol: rb_safe_level -
/usr/lib/x
Hi Dong,
I have been reading:
https://lore.kernel.org/kvm/CACGkMEs1t-ipP7TasHkKNKd=peVEES6Xdw1zSsJkb-
bc9et...@mail.gmail.com/T/#m167335bf7ab09b12fec3bdc5d46a30bc2e26cac7
and I tried to reproduce the problem with 23.10's userspace, but I can't
see the same crash.
By virtio legacy devices, you m
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs
Hi everyone,
An update:
Greg KH has picked up the patch and added it to upstream stable now:
https://lore.kernel.org/amd-gfx/2024061223-suitable-handler-b6f2@gregkh/
https://lore.kernel.org/amd-gfx/2024061239-rehydrate-flyable-343e@gregkh/
I suppose we can drop the UBUNTU: SAUCE tags.
I talke
Attached is a V2 that corrects a minor omission in the changelog.
** Patch added: "Debdiff for nvme-cli on Jammy V2"
https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/2051299/+attachment/5788982/+files/lp2051299_jammy_V2.debdiff
** Patch removed: "Debdiff for nvme-cli on Jammy"
http
it required a minor backport. In later versions, a major
refactor occurred that changed nvme_uuid_to_string() among numerous
other functions, that is not appropriate to backport. Instead, just take
the current implementation of nvme_uuid_to_string() and move it like the
patch suggests, so j
Hi Ariel,
Are you using zfs? I see you have the module listed.
Your oops looks very similar to this discussion here:
https://github.com/openzfs/zfs/issues/15140
It doesn't seem anyone has come to any conclusions yet. I'll do some
more research.
Thanks,
Matthew
** Bug watch added: github.com/o
Hi everyone,
Patches are on the Ubuntu Kernel Team mailing list:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-June/151409.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-June/151410.html
I will go talk to the kernel team now, I can't promise anything, but
will
** Summary changed:
- Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs
+ AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to
black screen
** Description changed:
- System is not booting while using AMD Picasso/Raven 2 graphics after
- update to
Hello Evgueni,
Are you sure it is an Nvidia card? We have a known regression for
5.15.0-112-generic with AMD cards, over in bug 2068738. The symptom is a
black screen on boot.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Hi Xie,
Thanks for trying the test kernel, and its great news that we have
identified the fix. I'll write up a SRU template, and get the patch sent
off to the kernel team today.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Tino,
It says Fix Released for Ubuntu, aka, the latest Ubuntu release, which
is 24.10 Oracular, as it isn't affected. Maybe I should have marked it
invalid in the first place.
Anyway, once someone tries the test kernel I built yesterday to see if
it fixes the issue, I can go about getting the
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068738
Title:
Kerne
PS. Please remove the workaround "nomodeset" if you applied it before
you try the test kernel. I really just want to know if the reverted
patch fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
** This bug has been marked a duplicate of bug 2068738
Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs
--
You received this bug notification because you are a member of Ubunt
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
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/206
*** This bug is a duplicate of bug 2068738 ***
https://bugs.launchpad.net/bugs/2068738
** This bug has been marked a duplicate of bug 2068738
Kernel update 5.15.0-112 might cause severe problems with specific AMD GPUs
--
You received this bug notification because you are a member of Ubunt
Hi Pramod,
Yes, this changed recently, in mantic and onward I believe.
CONFIG_DRM is set to "y" for all architectures except s390x, which is
why you still see drm.ko.zst for s390x only.
In Ubuntu Noble kernel sources:
debian.master/config/annotations:
177:CONFIG_DRM
Hi Daniel,
Thanks for your contributions!
There's two ways we get patches into our Ubuntu kernels, the first is a LP bug
per patchset that ideally fixes one specific issue, has a testcase etc and then
we submit patches for review to the Ubuntu Kernel Mailing list.
The process is:
https://wiki.ub
*** This bug is a duplicate of bug 2058052 ***
https://bugs.launchpad.net/bugs/2058052
** This bug has been marked a duplicate of bug 2058052
Enable Intel IDPF support on ARM64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
in: linux-gcp (Ubuntu Oracular)
Importance: Undecided => High
** Changed in: linux-gcp (Ubuntu Noble)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux-gcp (Ubuntu Oracular)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux
Public bug reported:
BugLink: https://bugs.launchpad.net/bugs/
[Impact]
GCE C3 Metal instance type requires the Intel IDPF driver for networking
to function.
On the Mantic kernel, this was built into the kernel:
# grep IDPF /boot/config-6.5.0-1020-gcp
CONFIG_IDPF=y
On Noble, this is now been
Attached is a debdiff which solves this issue for focal.
** Patch added: "Attached is a debdiff for ruby-curses on focal"
https://bugs.launchpad.net/ubuntu/+source/ruby-curses/+bug/1907932/+attachment/5779433/+files/lp1907932_focal.debdiff
--
You received this bug notification because you ar
Attached is a debdiff for jammy which solves this issue.
** Summary changed:
- ruby-curses: Emits warning: "rb_safe_level will be removed in Ruby 3.0",
affects at least irqtop
+ drop rb_safe_level() from ruby-curses to fix irqtop from missing symbols and
deprecation warnings
** Description cha
rses (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: ruby-curses (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: ruby-curses (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: ruby-curses (Ubuntu Jammy)
** Also affects: calibre (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** Also affects: calibre (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Hi Light_Kernel_Ops,
The linux-signed package is signed with Canonical's Secure Boot Signing
Key, making the kernel bootable on systems that have secure boot
enabled. This key is not public for obvious reasons, and only particular
Kernel team members have access to it.
Where do you want to publis
Hi Theodore,
Ubuntu carries a little delta ontop of debian, and requires a merge, so
I think it is best to wait a week for the final e2fsprogs release before
we perform the merge.
https://merges.ubuntu.com/e/e2fsprogs/REPORT
Thanks,
Matthew
--
You received this bug notification because you are
*** This bug is a duplicate of bug 2060780 ***
https://bugs.launchpad.net/bugs/2060780
Hi JB2Cool,
Yes, you are correct. You are seeing the exact same as bug 2060780, that
was introduced between 5.15.0-101 and 5.15.0-102 and fixed in
5.15.0-105.
For AWS, the fix is in:
$ git log --grep "smb
Hi Bernard,
These are userspace application crashes.
Try and wait for a kernel crash to occur.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064291
Title:
Ubuntu 24.04 crashed mu
Hi Bernard,
The crash seems to bring your system down before the logs are able to be
written to disk, so there is no oops present in your dmesg.
Its pretty common. Would you be able to capture a kernel crashdump
(kdump).
Follow the instructions in:
https://ubuntu.com/server/docs/kernel-crash-du
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Jammy)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: jammy sts
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux
Hi Sophi,
The 5.19 HWE kernel for Jammy is no longer supported. Its support period
was for the lifetime of the 22.10 Kinetic Kudu release, which is now end
of life.
Can you upgrade to a supported kernel, e.g. the latest 5.15 Jammy kernel
or the current 6.5 HWE kernel, and retry?
Is there any rea
Hi everyone,
Thank you for testing, and its great to hear that it fixes the issue.
The Jammy HWE kernel is still queued up to be built, it should be built
over the next few days. You can keep an eye on it at
https://kernel.ubuntu.com/reports/kernel-stable-board/
Regardless, we should be on track
Hi Bernard,
Can you have a look at your /var/log/kern.log and /var/log/syslog files,
and look for what is known as a kernel oops? It looks like some of the
examples in this bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060919
Would you be able to copy and paste any you find into a t
Hi everyone,
The kernel team has built the patch into the s2024.04.1 SRU cycle, as
6.5.0-35-generic.
An ETA for this is the week of 13th of May, as per
https://kernel.ubuntu.com/
Would anyone be able to help test the kernel by installing
6.5.0-35-generic from -proposed and doing a cifs mount and
Hi Krister,
Thanks for the heads up about 1.47.1 upstream, it does indeed look like
a release is coming soon.
It seems Debian unstable already has 1.7.1-rc1:
https://packages.debian.org/sid/e2fsprogs
When the Ubuntu archive opens for OO, we will merge 1.47.1~rc1-1 from
debian unstable, and then
Attached is a V2 patch for Noble for e2fsprogs.
** Patch added: "Debdiff for e2fsprogs on noble V2"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5772258/+files/lp2036467_noble_V2.debdiff
** Patch removed: "Debdiff for e2fsprogs on noble"
https://bugs.launch
Hi everyone,
Thanks for helping to test the test kernel, and I am glad that it fixes
the issue.
I have written a SRU template and have set it as the description of the
bug.
I have submitted the revert to the Kernel team mailing list for SRU:
Cover Letter:
https://lists.ubuntu.com/archives/kerne
** Summary changed:
- Remote filesystems mounted as CIFS not working after update to Kernel
"6.5.0-27-generic #28-Ubuntu" (amd64) or Kernel "6.5.0-1014-raspi #17-Ubuntu"
(aarch64).
+ cifs: Copying file to same directory results in page fault
** Description changed:
- Remote filesystems mounted
Hi Axel,
Sorry about you getting spammed about all these verifications. The robot
that posts these messages looks for the Launchpad bug number in the
package changelogs, and just makes a post for every package it sees it
in.
You might not know, but Ubuntu has slightly over 100 kernels these days,
) => (unassigned)
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned
** Changed in: linux (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049634
Title:
smb: wsize blocks of bytes followed with binary zeros on
h:
commit 9dc02a5b7540d18a69bcbaf8f4fa428e32075b4b (HEAD -> lp2060919-test)
Author: Matthew Ruffell
Date: Fri Apr 19 17:25:48 2024 +1200
Revert "cifs: fix flushing folio regression for 6.1 backport"
This reverts commit 21bb2ba4f1ac1e3a57594be62dd74e7b1401b2b1.
dif
Hello,
I can't actually reproduce the issue, I seem to be missing something.
Server
--
$ sudo apt update
$ sudo apt upgrade
$ sudo apt install samba
$ sudo vim /etc/samba/smb.conf
server min protocol = NT1
[sambashare]
comment = Samba on Ubuntu
path = /home/ubuntu/sambashare
read
Hi everyone,
5.15.0-105-generic has been released to -updates now. It fixes the cifs
issue.
https://launchpad.net/ubuntu/+source/linux/5.15.0-105.115
Please let us know if you find any more issues.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Performing verification for Focal.
I started two VMs, one Jammy, which is the nfs server, and one Focal,
which is the client. I used the instructions in the testcase sections of
this bug, and also bug 2049262.
The Focal VM has nfs-common 1:1.3.4-2.5ubuntu3.6 from -updates.
Let's try the testcase
*** This bug is a duplicate of bug 2060780 ***
https://bugs.launchpad.net/bugs/2060780
** This bug has been marked a duplicate of bug 2060780
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
--
You received this bug notification because you are a member of Ubuntu
Bugs
Performing verification for Jammy.
I started two Jammy VMs. One is a server and the other a client.
Server
--
$ sudo apt update
$ sudo apt upgrade
$ sudo apt install samba
$ sudo vim /etc/samba/smb.conf
[sambashare]
comment = Samba on Ubuntu
path = /home/ubuntu/sambashare
read on
Hi everyone, the fix will also be available for Focal, as part of it
getting the Jammy HWE kernel. It will be released at the same time as
Jammy's kernel is released.
We got the notification above that the kernel should be in -proposed,
but I have been refreshing -proposed all day and the kernel i
The new kernel is tagged as 5.15.0-105-generic, and it is a respin of
5.15.0-103-generic with the fix.
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/jammy/log/?h=Ubuntu-5.15.0-105.115
It should be available in -proposed soon, the Kernel Team are still
rebuilding all the 5.15
*** This bug is a duplicate of bug 2060780 ***
https://bugs.launchpad.net/bugs/2060780
Come over to bug 2060780 and talk about it with us there.
** This bug has been marked a duplicate of bug 2060780
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
--
You received th
Hi everyone,
5.15.0-104-generic just hit jammy-proposed a couple minutes ago. It
isn't available for focal users yet.
Can someone please test 5.15.0-104-generic on jammy and let me know if
it fixes the issue? Thanks.
Instructions to Install (On a mantic system):
1) cat << EOF | sudo tee /etc/apt
Thanks for pointing out the missing patch Heitor. I was indeed missing
it.
Please review and sponsor the V2 debdiff.
Thanks,
Matthew
--
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:
mo
Sanity testing the test package:
https://launchpad.net/~mruffell/+archive/ubuntu/lp2059197-test
nfs-common 1:1.3.4-2.5ubuntu3.6+lp2059197v20240411b1
Testcase for this bug, i.e. the regression.
$ sudo mount -t nfs4 -o vers=4.2 -vvv jammy-nfs-server:/ /mnt
mount.nfs4: timeout set for Thu Apr 11 0
Hi everyone,
Reading:
https://lore.kernel.org/lkml/2024020616.454699-1-kova...@altlinux.org/T/
It seems the issue was introduced in
commit 33eae65c6f49770fec7a662935d4eb4a6406d24b
Author: Paulo Alcantara
Date: Wed Dec 13 12:25:57 2023 -0300
Subject: smb: client: fix OOB in SMB2_query_inf
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Tags added: seg
--
You received this bug notification because you ar
*** This bug is a duplicate of bug 2060780 ***
https://bugs.launchpad.net/bugs/2060780
Hi everyone, I will provide updates on the other bug 2060780.
** This bug has been marked a duplicate of bug 2060780
CIFS stopped working/is unstable with kernel update to 5.15.0-102.112
--
You receive
Attached is a new debdiff which includes the missing patch. I did
another look upstream, but I think we are okay now.
** Patch added: "Debdiff for nfs-utils on Focal V2"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+attachment/5763564/+files/lp2059197_focal_V2.debdiff
** C
** Patch removed: "Debdiff for nfs-utils on Focal"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2059197/+attachment/5761398/+files/lp2059197_focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Hi R. Diez,
The 6.5.0-27-generic kernel just got released, so it should make its way
to an archive mirror near you in the next couple of hours, and should
solve your SMB 1 issue. The 6.8 kernel should be good to go when you get
it in the next couple of months.
Let us know if you encounter any mor
Hi Jeff,
Again, I apologise for introducing this regression, but we are on our
way to getting this fixed.
The fixes are:
commit 1e3ca7fe199531a372bb8e1c1033d8973097be50
Author: NeilBrown
Date: Wed Jul 26 13:47:42 2017 -0400
Subject: mount: move handling of "-t nfs4" into nfs_nfs_version()
Lin
Attached is a debdiff for Focal which fixes this issue.
** Summary changed:
- Issue with nfs4.0 mounts after upgrade to 3.6
+ Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used together
** Summary changed:
- Fix minor version parsing when '-t nfs4' and '-o vers=4.x' are used to
untu)
Status: New => Fix Released
** Changed in: nfs-utils (Ubuntu Focal)
Status: New => In Progress
** Changed in: nfs-utils (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: nfs-utils (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
-
** Changed in: systemd (Ubuntu Focal)
Status: New => In Progress
** Changed in: systemd (Ubuntu Focal)
Importance: Low => Medium
** Changed in: systemd (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Tags added: sts
--
You received this bug not
Thank you for the help sorting autopkgtests Mauricio.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2033892
Title:
ls -l triggers mount of autofs shares when --ghost option is present
or browse_mo
Performing verification for Jammy
I set up two Jammy VMs, one a nfs-server and the other an autofs/nfs-
client.
The client is using coreutils 8.32-4.1ubuntu1.1 from -updates.
$ apt-cache policy coreutils | grep Installed
Installed: 8.32-4.1ubuntu1.1
I set up the nfs server and autofs mounts
Performing verification for mantic.
I deployed mantic onto a bare metal server, with kernel 6.5.0-26-generic from
-updates.
I installed a KVM stack, synced a cloud image, and tested VM creation.
$ uvt-kvm create --cpu 4 --memory 4096 --disk 10 jammy-a release=jammy
arch=amd64
$ uvt-kvm ssh jamm
gtkpod has been removed from debian, and thus removed from noble, so no
need to fix there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults when attempting to display so
Attached is a debdiff for mantic which fixes this issue.
** Patch added: "Debdiff for gtkpod on mantic"
https://bugs.launchpad.net/ubuntu/+source/gtkpod/+bug/2044420/+attachment/5757356/+files/lp2044420_mantic.debdiff
** Changed in: glib2.0 (Ubuntu Noble)
Status: Triaged => Fix Release
Performing verification for Jammy.
I started a fresh VM, with 5.15.0-101-generic from updates. I ran the
following reproducer:
$ fallocate -l 1G /tmp/blob
$ LOOPDEV=$(sudo losetup --find --show /tmp/blob)
$ sudo /usr/sbin/parted -s -m -a optimal $LOOPDEV -- unit KiB mklabel gpt
mkpart primary 0%
The fix for noble should be present in 6.8.0-16-generic and later.
Marking as Fix committed for Noble.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049634
Title:
smb: wsize blocks of bytes followe
Performing verification for mantic.
I started two VMs. A jammy VM for the cifs server, and a mantic VM, for
the client.
I set the jammy VM up as per the testcase.
I set the mantic VM up as per the testcase.
The mantic VM uses kernel 6.5.0-25-generic from -updates.
$ uname -rv
6.5.0-25-generic
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049634
Title:
smb: wsize blocks of bytes followed with binary zeros on
Hi Rainer.
I think we will leave it as is. Keep using v4.0 for now, and you should
be fine.
I'll close the bug.
Andreas, I will remove regression-update if that is okay with you.
Thanks,
Matthew
** Changed in: nfs-utils (Ubuntu Focal)
Status: New => Invalid
** Changed in: nfs-utils (Ub
Hi Rainer,
Thanks for trying that out, and it is great to hear that v4.0 works for
you, and you added it to your /etc/fstab as a good workaround for the
meantime.
Are you interested in debugging why your system hangs when trying v4.2
and v4.1? or do you want to leave it there? 4.0 will keep worki
I think the fix was included in 5.15.149 upstream;
https://lwn.net/Articles/963359/
Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID
The kernel team have just pulled in 5.15.148, and haven't started on
149. They will likely get to it in the next week or so.
Thanks,
Matthew
-
Hi Rainer,
Thanks for the screenshots.
The updated package changes how the '-o vers=4' parameter works. The old
/ wrong behaviour would always use nfs v4.0 no matter what. All other
nfs-common versions apart from the version in focal would try v4.2, then
if that didn't work, then v4.1, and then v
Hi Rainer,
I developed the nfs-utils update of 1:1.3.4-2.5ubuntu3.6, and I am very
interested to hear more about the possible regression.
The intention was to fix version negotiation when using the '-t nfs4' or
'-o vers=4' parameters in your mount command. You can find more about it
here:
https:
Yes, 6.5.0-25-generic is available for both jammy and mantic systems. It
was released earlier this week.
Is anyone able to try it out and let me know if it fixes the issue?
Thanks.
** Changed in: linux (Ubuntu Mantic)
Status: Fix Committed => Fix Released
--
You received this bug notific
*** This bug is a duplicate of bug 2046844 ***
https://bugs.launchpad.net/bugs/2046844
Hi cipricus,
This is a security feature working as intended. Ubuntu recently decided
to disable unprivileged access to user namespaces. You can find more
information it about it here:
https://ubuntu.com/bl
Hi Sly,
We do actually test as many dkms builds as we can. Well, mainly all the
kernel modules present in the Ubuntu archive, like evdi-dkms.
The trouble starts when you get dkms sources from other places that we
don't know about, like the DisplayLink installer that I linked above.
You, me, and o
Hi Sly,
Your evdi kernel module for DisplayLink docks failed to compile. It
likely couldn't generate your initramfs, leaving your 6.5.0-21-generic
not able to boot.
Your logs say its trying to build version 1.11.0:
ERROR (dkms apport): binary package for evdi: 1.11.0 not found
Error! Bad return
Hi everyone,
@angros47, yes, this issue looks to be what you are experiencing here.
https://bugs.archlinux.org/task/80064 mentions that the issue was
introduced in:
commit aa3998dbeb3abce63653b7f6d4542e7dcd022590
Author: Damien Le Moal
Date: Sat Aug 26 09:43:39 2023 +0900
Subject: ata: libata
Reviews from Senior Kernel Team Members:
ACK 1
https://lists.ubuntu.com/archives/kernel-team/2024-February/149051.html
ACK 2
https://lists.ubuntu.com/archives/kernel-team/2024-February/149061.html
Applied
https://lists.ubuntu.com/archives/kernel-team/2024-February/149119.html
Will let you know wh
Performing verification for Focal.
I set up a Jammy VM to be the nfs server, using the instructions in the
SRU template.
$ sudo cat /proc/fs/nfsd/versions
-2 -3 +4 -4.0 +4.1 +4.2
4.0 is not allowed, but 4.1 and 4.2 are.
I then started a fresh Focal VM, and installed nfs-common
1.3.4-2.5ubuntu3.
Performing verification for Bionic.
Bionic seems to hibernate okay on both Xen and KVM based instances, so I tested
both t2.medium and c5.large instance types. Each had 20gb of storage, with
advanced > enable encryption > yes.
I also made sure to enable Advanced settings > Stop State (Hibernatio
*** This bug is a duplicate of bug 1967843 ***
https://bugs.launchpad.net/bugs/1967843
This is probably fixed in clutter-gst-3.0 3.0.27-2ubuntu1 that we
released a couple days ago. Run "sudo apt update" and "sudo apt upgrade"
and it will pull in the fixed package.
Marking as a duplicate of bu
*** This bug is a duplicate of bug 1967843 ***
https://bugs.launchpad.net/bugs/1967843
This is probably fixed in clutter-gst-3.0 3.0.27-2ubuntu1 that we
released a couple days ago. Run "sudo apt update" and "sudo apt upgrade"
and it will pull in the fixed package.
Marking as a duplicate of bu
Performing verification for Jammy.
For some reason hibernation just refused to work on any Xen based
instance type, but it works fine on KVM based instances, such as c5, t3
etc. This is being looked into on bug 1968062, but I think it affects
Jammy as well.
Diverging from the testcase, and using
Performing verification for Impish.
For some reason hibernation just refused to work on any Xen based
instance type, but it works fine on KVM based instances, such as c5, t3
etc. This is being looked into on bug 1968062, but I think it affects
Impish as well.
Diverging from the testcase, and usin
Performing verification for Focal.
For some reason hibernation just refused to work on any Xen based
instance type, but it works fine on KVM based instances, such as c5, t3
etc. This is being looked into on bug 1968062, but I think it affects
Focal as well.
Diverging from the testcase, and using
Hi Henning,
That is great news that "intel_iommu=off" on the kernel command line did
the trick.
You can follow this bug to get updates on when we will be disabling
IOMMU by default in the 5.15 kernel. It should be soon, the patches are
already submitted, and reviewed by the kernel team. The next
A user has reported extensive performance issues with a Lenovo Thinkpad
X1 Extreme Gen 2 laptop computer, in bug 1973434. The user reports video
playback hangs, browser hangs and virtual machines hanging.
Their dmesg indicates the system has 2x IOMMUs and there are 25 groups
being configured. They
Hi Henning,
Just a thought, could you try booting with IOMMU disabled?
Edit /etc/default/grub, and append "intel_iommu=off" to
GRUB_CMDLINE_LINUX_DEFAULT. Then save, and run "sudo update-grub" and
reboot.
Between 21.10 and 22.04 we enabled CONFIG_INTEL_IOMMU_DEFAULT_ON=y, and
it has caused all s
Performing verification for Jammy.
Starting with the broken 3.0.27-2build2 in -release, running
gst-launch-1.0 videotestsrc ! jpegenc ! jpegdec ! clutterautovideosink
shows a grey picture with vertical bars. Opening cheese, we see the same
vertical bars, poor video performance and purple lines.
A user has ran into a storage performance issue, and it has been traced
back to CONFIG_INTEL_IOMMU_DEFAULT_ON being enabled.
They have a Dell XtremIO FC storage server, running VMWare ESXi 7.0U3,
with 4x pvscsi controllers (2 LUNs per controller), running a single
large LV with 8-way 1MB stripe.
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971699
Title:
disable Intel DMA remapping by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
101 - 200 of 829 matches
Mail list logo
