** Description changed:
+ The Nvidia driver corrupts and/or forgets its textures when resuming
+ from suspend. Unfortunately for the moment it's a "feature" of the
+ Nvidia driver documented here:
+
+
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
+
given how zfs works, to me this is normal and expected.
Also this is expected on btrfs, and on xfs with cow turned on.
zfs is copy on write filesystem, thus calling fallocate to "reserve" a
large amount of free space doesn't make sense. As the created file is
immutable in zfs, and any writes to
Public bug reported:
Fresh installation of 20.04.4 with installer created zfs native encrypted root
zfsutils-linux: 0.8.3-1ubuntu12.13
On reboot, zvol /dev/zvol entries are not being created. This seems to
effect different zvols each reboot.
Example logs:
```
-- A start job for unit
This bug was fixed in the package linux-azure - 5.4.0-1077.80
---
linux-azure (5.4.0-1077.80) focal; urgency=medium
* focal/linux-azure: 5.4.0-1077.80 -proposed tracker (LP: #1968796)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
Commit "s390/pci: move pseudo-MMIO to prevent MIO overlap" landed in impish
with hash 35705e7746d4 and is included in impish's kernel 'Ubuntu-5.13.0-36.41'
and later.
Latest kernel in impish-updates is linux-generic | 5.13.0.40.49 |
impish-updates
hence this incl. the needed commit.
With that
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.60.02-0ubuntu0.21.10.2
---
nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.21.10.2) impish; urgency=medium
[ Jeremy Szu ]
* Fix regex in modalias addition, since it does not work
in dash (LP: #1964756)
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.60.02-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.20.04.2) focal; urgency=medium
[ Jeremy Szu ]
* Fix regex in modalias addition, since it does not work
in dash (LP: #1964756).
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux-azure - 5.4.0-1077.80
---
linux-azure (5.4.0-1077.80) focal; urgency=medium
* focal/linux-azure: 5.4.0-1077.80 -proposed tracker (LP: #1968796)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.147-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-390 (390.147-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1966093):
- Fixed a bug where vkCreateSwapchain could cause the X Server to
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.60.02-0ubuntu0.21.10.2
---
nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.21.10.2) impish; urgency=medium
[ Jeremy Szu ]
* Fix regex in modalias addition, since it does not work
in dash (LP: #1964756)
This bug was fixed in the package linux-azure - 5.4.0-1077.80
---
linux-azure (5.4.0-1077.80) focal; urgency=medium
* focal/linux-azure: 5.4.0-1077.80 -proposed tracker (LP: #1968796)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug is awaiting verification that the linux/5.13.0-41.46 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-41.46 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-impish' to 'verification-done-impish'. If the
problem still exists,
Impish kernel on zfs:
andreas@nsnx:~$ rm foo.img
andreas@nsnx:~$ touch foo.img
andreas@nsnx:~$ fallocate -z -l 10M foo.img
fallocate: fallocate failed: Operation not supported
Jammy kernel on zfs:
root@j1:~# touch foo.img
root@j1:~# fallocate -z -l 10M foo.img
root@j1:~# ll foo.img
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-gcp - 5.4.0-1072.77
---
linux-gcp (5.4.0-1072.77) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1072.77 -proposed tracker (LP: #1968829)
* Miscellaneous Ubuntu changes
- [packaging] Update annotations for arm64
- [packaging]
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1033.36
---
linux-oem-5.14 (5.14.0-1033.36) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1033.36 -proposed tracker (LP:
#1967397)
* Bolt doesn't work with native USB4 hosts (LP: #1962349)
- thunderbolt: Retry
However there is now also this:
https://github.com/openzfs/zfs/pull/13338/files
which seems to indicate that my / zfs understanding of the fallocate
kernel flags are not what is done on other filesystems (and expected by
stuff).
If needed, we can look into pulling in
imho, mysql should still gain zfs specific knowledge that doing
fallocate on CoW filesystems doesn't do what one expects it to do.
** Changed in: mysql-8.0 (Ubuntu)
Status: Invalid => Triaged
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug
This bug is awaiting verification that the linux-
intel-5.13/5.13.0-1011.11 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-focal' to 'verification-
done-focal'. If the problem still
This bug is awaiting verification that the linux-
intel-5.13/5.13.0-1011.11 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-focal' to 'verification-
done-focal'. If the problem still
This bug is awaiting verification that the linux-
intel-5.13/5.13.0-1011.11 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-focal' to 'verification-
done-focal'. If the problem still
This bug is awaiting verification that the linux-
intel-5.13/5.13.0-1011.11 kernel in -proposed solves the problem. Please
test the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-focal' to 'verification-
done-focal'. If the problem still
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.147-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-390 (390.147-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1966093):
- Fixed a bug where vkCreateSwapchain could cause the X Server to
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.147-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-390 (390.147-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1966093):
- Fixed a bug where vkCreateSwapchain could cause the X Server to
This bug was fixed in the package linux - 4.15.0-176.185
---
linux (4.15.0-176.185) bionic; urgency=medium
* bionic/linux: 4.15.0-176.185 -proposed tracker (LP: #1966771)
* Bionic update: upstream stable patchset 2022-03-04 (LP: #1963717)
- can: bcm: fix UAF of bcm op
-
This bug was fixed in the package linux - 4.15.0-176.185
---
linux (4.15.0-176.185) bionic; urgency=medium
* bionic/linux: 4.15.0-176.185 -proposed tracker (LP: #1966771)
* Bionic update: upstream stable patchset 2022-03-04 (LP: #1963717)
- can: bcm: fix UAF of bcm op
-
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.60.02-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-510 (510.60.02-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1966093):
- Added support for the following GPUs:
NVIDIA RTX
The jammy RC (20220418.2) looks good for Ampere Mt. Jade Altra (bizzy).
I can pxe install the server successfully.
By the way autoinstall of subiquity also works like a charm.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This bug was fixed in the package linux-azure - 5.4.0-1077.80
---
linux-azure (5.4.0-1077.80) focal; urgency=medium
* focal/linux-azure: 5.4.0-1077.80 -proposed tracker (LP: #1968796)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux - 5.4.0-109.123
---
linux (5.4.0-109.123) focal; urgency=medium
* focal/linux: 5.4.0-109.123 -proposed tracker (LP: #1968290)
* USB devices not detected during boot on USB 3.0 hubs (LP: #1968210)
- SAUCE: Revert "Revert "xhci: Set HCD
This bug was fixed in the package linux-azure-cvm - 5.4.0-1076.79+cvm1
---
linux-azure-cvm (5.4.0-1076.79+cvm1) focal; urgency=medium
* focal/linux-azure-cvm: 5.4.0-1076.79+cvm1 -proposed tracker (LP:
#1968347)
* Packaging resync (LP: #1786013)
- debian/dkms-versions --
This bug was fixed in the package linux-gcp - 5.4.0-1072.77
---
linux-gcp (5.4.0-1072.77) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1072.77 -proposed tracker (LP: #1968829)
* Miscellaneous Ubuntu changes
- [packaging] Update annotations for arm64
- [packaging]
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962831
Title:
[UBUNTU 20.04] KVM: Enable storage key
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962578
Title:
[UBUNTU 20.04] Fix SIGP processing on KVM/s390
The impish kernel returns "not supported" when fallocate is used in the
way mysql does it. That makes mysql aware of the problem, and switch
strategies, and it works.
The jammy kernel is saying all is fine with the call and its results,
but it isn't. Mysql, or any userspace, shouldn't be second
** Description changed:
+ [Impact]
+
The Nvidia driver corrupts and/or forgets its textures when resuming
from suspend, by design. Documented here:
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
Although it's so awkward to implement
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Impish)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux - 5.13.0-40.45
---
linux (5.13.0-40.45) impish; urgency=medium
* impish/linux: 5.13.0-40.45 -proposed tracker (LP: #1966701)
* CVE-2022-1016
- netfilter: nf_tables: initialize registers in nft_do_chain()
* CVE-2022-1015
-
This bug was fixed in the package linux - 5.13.0-40.45
---
linux (5.13.0-40.45) impish; urgency=medium
* impish/linux: 5.13.0-40.45 -proposed tracker (LP: #1966701)
* CVE-2022-1016
- netfilter: nf_tables: initialize registers in nft_do_chain()
* CVE-2022-1015
-
This bug was fixed in the package linux - 5.13.0-40.45
---
linux (5.13.0-40.45) impish; urgency=medium
* impish/linux: 5.13.0-40.45 -proposed tracker (LP: #1966701)
* CVE-2022-1016
- netfilter: nf_tables: initialize registers in nft_do_chain()
* CVE-2022-1015
-
This bug was fixed in the package linux - 5.13.0-40.45
---
linux (5.13.0-40.45) impish; urgency=medium
* impish/linux: 5.13.0-40.45 -proposed tracker (LP: #1966701)
* CVE-2022-1016
- netfilter: nf_tables: initialize registers in nft_do_chain()
* CVE-2022-1015
-
This bug was fixed in the package linux - 5.13.0-40.45
---
linux (5.13.0-40.45) impish; urgency=medium
* impish/linux: 5.13.0-40.45 -proposed tracker (LP: #1966701)
* CVE-2022-1016
- netfilter: nf_tables: initialize registers in nft_do_chain()
* CVE-2022-1015
-
This bug was fixed in the package linux - 5.13.0-40.45
---
linux (5.13.0-40.45) impish; urgency=medium
* impish/linux: 5.13.0-40.45 -proposed tracker (LP: #1966701)
* CVE-2022-1016
- netfilter: nf_tables: initialize registers in nft_do_chain()
* CVE-2022-1015
-
This bug was fixed in the package linux-azure - 5.13.0-1022.26
---
linux-azure (5.13.0-1022.26) impish; urgency=medium
* impish/linux-azure: 5.13.0-1022.26 -proposed tracker (LP: #1967347)
* linux-azure: CONFIG_HIBERNATION=y (LP: #1967336)
- [Config] Azure: arm64
This bug was fixed in the package linux - 5.13.0-40.45
---
linux (5.13.0-40.45) impish; urgency=medium
* impish/linux: 5.13.0-40.45 -proposed tracker (LP: #1966701)
* CVE-2022-1016
- netfilter: nf_tables: initialize registers in nft_do_chain()
* CVE-2022-1015
-
This bug was fixed in the package linux - 5.13.0-40.45
---
linux (5.13.0-40.45) impish; urgency=medium
* impish/linux: 5.13.0-40.45 -proposed tracker (LP: #1966701)
* CVE-2022-1016
- netfilter: nf_tables: initialize registers in nft_do_chain()
* CVE-2022-1015
-
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.147-0ubuntu0.21.04.1
---
nvidia-graphics-drivers-390 (390.147-0ubuntu0.21.04.1) impish; urgency=medium
* New upstream release (LP: #1966093):
- Fixed a bug where vkCreateSwapchain could cause the X Server to
** Tags added: jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchpad.net/bugs/1876632
Title:
[nvidia] Corrupted/missing shell textures when switching users or
resuming
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-42.1 fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
This bug was fixed in the package linux-aws - 5.13.0-1022.24
---
linux-aws (5.13.0-1022.24) impish; urgency=medium
* impish/linux-aws: 5.13.0-1022.24 -proposed tracker (LP: #1967345)
* linux-aws: Xen: Issues with detaching volume (LP: #1966969)
- xen-blkfront: sanitize the
The verification of the Stable Release Update for nvidia-graphics-
drivers-390 has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the
This bug was fixed in the package linux-azure - 5.13.0-1022.26
---
linux-azure (5.13.0-1022.26) impish; urgency=medium
* impish/linux-azure: 5.13.0-1022.26 -proposed tracker (LP: #1967347)
* linux-azure: CONFIG_HIBERNATION=y (LP: #1967336)
- [Config] Azure: arm64
This bug was fixed in the package linux-azure - 5.13.0-1022.26
---
linux-azure (5.13.0-1022.26) impish; urgency=medium
* impish/linux-azure: 5.13.0-1022.26 -proposed tracker (LP: #1967347)
* linux-azure: CONFIG_HIBERNATION=y (LP: #1967336)
- [Config] Azure: arm64
** Description changed:
The Nvidia driver corrupts and/or forgets its textures when resuming
from suspend, by design. Documented here:
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
Although it's so awkward to implement everywhere that
Hi Tiago,
The kernel team have reviewed the patch, and it has received 2x acks [1]
and it has been applied [2] to the Jammy kernel git tree [3].
[1] https://lists.ubuntu.com/archives/kernel-team/2022-April/129208.html
[2] https://lists.ubuntu.com/archives/kernel-team/2022-April/129498.html
[3]
My USB device outputs popping noise on the 44100Hz sample rate with JACK
in 5.13.0-37. This seems to be similar issue on this bug.
Related Discussion:
https://askubuntu.com/questions/1399136/sound-not-working-on-ubuntu-20-04
In my case, downgrading to 5.13.0-35 fixed this issue.
cd ~/Desktop
** Changed in: linux-azure (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member
** Also affects: linux-azure (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-azure
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-impish
** Tags added: verification-done verification-done-bionic
verification-done-focal verification-done-impish
--
You received this bug notification because you are a member of
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided => High
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Status: Confirmed => Triaged
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Importance: Undecided => High
** Changed in:
jammy needs sru too at this point
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1966841
Title:
alsa/sdw: Fix the audio issue on a Dell machine without internal mic
Status in
I applied zfs_fallocate_reserve_percent=0 to the kernel module,
confirmed it was set, but I still see the same incorrect behavior with
fallocate:
root@nsn7:/tank/test# rm -f foo.img; touch foo.img; fallocate -z -l 10M
foo.img; ls -lah foo.img
-rw-r--r-- 1 root root 0 abr 19 10:35 foo.img
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux-oem-5.14 (Ubuntu Jammy)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1968892
Title:
Micmute LED support for
On jammy, it works on btrfs:
root@nsn7:/mnt# rm -f foo.img; touch foo.img; fallocate -z -l 10M foo.img; ls
-lah foo.img
-rw-r--r-- 1 root root 10M abr 19 10:46 foo.img
root@nsn7:/mnt# mount -t btrfs
/btrfs.img on /mnt type btrfs
(rw,relatime,ssd,space_cache=v2,subvolid=5,subvol=/)
--
You
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
I'm sorry, it looks like I won't be able to validate this fix on our
Ubuntu Core 20 systems. While waiting for this fix to become available,
we've used Ubuntu Core's refresh control (snap gating) mechanism to
ensure a non-affected version of the pc-kernel snap is installed across
our fleet of
Thanks!
The picture in comment #4 contains the full stack trace.
Some technical analysis for reference. Don't worry about it.
Please see the next comment for suggestions, for now.
...
When returning to userspace from the exit_group() syscall
(as per: orig rax == 0xe7 == 231 -> sys_exit_group;
** Patch added: "backport-iwlwifi-dkms_9858-0ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/focal/+source/linux-oem-5.17/+bug/1969434/+attachment/5581484/+files/backport-iwlwifi-dkms_9858-0ubuntu3.debdiff
--
You received this bug notification because you are a member of Kernel
Packages,
Prebuilt PPA in
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1969434
** Merge proposal linked:
https://code.launchpad.net/~vicamo/ubuntu/+source/backport-iwlwifi-dkms/+git/backport-iwlwifi-dkms/+merge/419698
--
You received this bug notification because you are a member of Kernel
** Changed in: mysql-8.0 (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969247
Title:
fallocate with FALLOC_FL_ZERO_RANGE produces
Public bug reported:
[Impact]
* Upstream stable point release update with bugfixes, performance
fixes, and newer kernel support as will be needed in the future hwe
kernels.
[Test Plan]
* autopkgtest pass
* kernel regression zfs testsuite pass
* zsys integration test pass
[Where
This bug is awaiting verification that the linux/5.4.0-110.124 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change
This bug is awaiting verification that the linux/5.4.0-110.124 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-focal' to 'verification-done-focal'. If the problem
still exists, change
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967754
Title:
ubuntu 22.04 jammy, mlx5, can't change flow
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1969434
and then change the status of the bug to 'Confirmed'.
If, due to the
** Summary changed:
- dkms.conf doesn't respect --kernelsourcedir passed to dkms build
+ build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI
** Description changed:
+ [backport-iwlwifi-dkms]
+
Under some circumstances, dkms is invoked as: `/usr/sbin/dkms build
--kernelsourcedir ...`
1 - 100 of 131 matches
Mail list logo
