Thanks for testing this!
--
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/1966499
Title:
Recent 5.13 kernel has broken KVM support
Status in linux package in Ubuntu:
Fix Released
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** 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
Mark unsupported series as Won't fix.
** Changed in: linux (Ubuntu Hirsute)
Status: Fix Committed => Won't Fix
** Changed in: linux-oem-5.10 (Ubuntu Focal)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1968902
Title:
ARM64_SW_TTBR0_PAN Should Be
*** This bug is a duplicate of bug 1966066 ***
https://bugs.launchpad.net/bugs/1966066
Mark it as dup for bug 1966066, please feel free to unmark it if you
think this is incorrect.
** This bug has been marked a duplicate of bug 1966066
audio from external sound card is distorted
--
You
ADT test started correctly.
** Tags removed: verification-needed-focal verification-needed-impish
** Tags added: verification-done-focal verification-done-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
Hi, Jeff
Is there any updates? is there a fixed kernel for us test?
--
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/1968519
Title:
[Lenovo Ubuntu 22.04 Bug]The Physical VGA displayer
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Focal 5.4.0-110.124 with node spitfire:
Running
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test'
BUILD_HEAD=16647354
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot
-nodefaults -device pc-testdev -device
Impish 5.13 with node vought:
Running
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/vmx_ldtr_test'
BUILD_HEAD=16647354
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 --no-reboot
-nodefaults -device pc-testdev -device
wuwei912 (wuwei912), please give the proposed kernel mentioned in #40 a
try, thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1966066
Title:
audio from external
** Information type changed from Public Security to Public
--
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/1964827
Title:
zfs-linux upstream at 2.1.4, jammy has 2.1.2
Status in
Hi Dries,
Please do not feel a rush to validate the fix, I was more asking just to
confirm personally that your issue has been resolved :)
That message about dropping the fix is more of an empty threat by a bot
than anything else..
So feel free at your earliest convenience to update and confirm
No changes with 5.13.0-40-generic #45-Ubuntu SMP Tue Mar 29 14:48:14 UTC
2022 to the issues described here:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-
hwe-5.13/+bug/1966066/comments/36
Have to resort to the partial fix with the patchend kernel, mentionened here,
still:
Confirmed fixed for me on linux-generic-hwe-20.04 version 5.13.0-41.46
from impish-proposed.
(edit: whoops, got the version wrong)
eta@st-pancras ~> uname -a
Linux st-pancras 5.13.0-41-generic #46-Ubuntu SMP Thu Apr 14 20:06:04 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux
** Tags removed:
** Also affects: linux-bluefield (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: linux-bluefield (Ubuntu)
Assignee: (unassigned) => Zachary Tahenakos (ztahenakos)
** Changed in:
Works great on my side with the 5.13.0-41.46 kernel.
VM start correctly and no more log spamming.
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Changed in: linux-bluefield (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1969374
Title:
linux-bluefield: Fix build failure in
SRU: https://lists.ubuntu.com/archives/kernel-
team/2022-April/129581.html (oem-5.15, jammy, oem-5.17, unstable)
** Description changed:
+ [SRU Justfication]
+
+ [Impact]
+
+ Intel AX211 iwlwifi -64 firmware may fail to init under reboot stress,
+ and -67 is immune. FW API -64 supported by
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
Tested:
./jammy/amd64/linux-modules-iwlwifi-5.15.0-27-generic_5.15.0-27.28_amd64.deb
./jammy/amd64/linux-modules-iwlwifi-generic_5.15.0-27.28_amd64.deb
./unstable/amd64/linux-modules-iwlwifi-5.17.0-8-generic_5.17.0-8.8_amd64.deb
./unstable/amd64/linux-modules-iwlwifi-generic_5.17.0-8.8_amd64.deb
The attachment "backport-iwlwifi-dkms_9858-0ubuntu3.debdiff" seems to be
a debdiff. The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff. If
the attachment isn't a patch, please remove the "patch" flag from the
attachment,
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
** 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,
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
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
This seems to be a nouveau/nvidia drivers topic.
I'm not a graphics expert, but if I recall correctly,
the opensource `nouveau` driver is usually disabled in
favor of the proprietary `nvidia` drivers, which seem
to work better on the Nvidia cards/gpus.
I can't provide the detailed steps right
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;
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 ...`
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
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 Jammy)
Status: In Progress => 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/1952933
Title:
impish kernel crashes on hp m400 in
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/1966194
Title:
[Jammy, mlx5, ConnectX-7] add CX7 support for
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 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: 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
yeap that's bad.
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: zfs-linux (Ubuntu)
Importance: Wishlist => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
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
** 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
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
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
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
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
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
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
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-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 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
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,
** 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
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-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
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 - 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 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 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 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 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-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 - 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 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
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 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
1 - 100 of 131 matches
Mail list logo
