** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2044091
Title:
Long
** Description changed:
[Impact]
WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting.
[Fix]
Realtek provides a patchset to enable this feature
https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t
The patchset has been included
@toekneefan I know the workforce is always limited and I don't want to
blame anyone. After all, I'm not paying for support.
However, silent data corruption in a file system that is supposed to
first and foremost prevent silent data corruption is a serious defect,
and I understand that people are
I have the same issue. Kubuntu 22.04, after sleep/screen lock my usb-c
-> display port connected monitor goes from 5120x1440 down to 3840x2160.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
affects 6.2.0-1011-aws -> 6.2.0-1016-aws, 6.2.0-1011-azure ->
6.2.0-1016-azure kernels, did not affect 5.19 and prior kernels in
22.04.2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-aws-6.2 in Ubuntu.
** Description changed:
[Impact]
+ WIFI 6/6E GHz should be enabled/disabled depends on the BIOS setting.
[Fix]
+ Realtek provides a patchset to enable this feature
+
https://lore.kernel.org/linux-wireless/20231114091359.50664-1-pks...@realtek.com/T/#t
+
+ The patchset has been included
** Tags added: oem-priority originate-from-2044087 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2045622
Title:
RTL8852CE WIFI read country list supporting 6 GHz
Public bug reported:
[Impact]
[Fix]
[Test case]
[Where problems could occur]
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects:
[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.
[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.
[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.
[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.
** Tags added: originate-from-2042412
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2044096
Title:
Support Cirrus CS35L41 codec on Dell Oasis 13/14/16 laptops
Status in HWE
@mafoelffen I'm sure the developers are hard at work with this and other
issues.
Ubuntu LTS, I believe, does not yet have coreutils v9, so it is unlikely
to be affected. This bug is actually extremely old (possibly going back
almost two decades), but recent changes, such as a change to
** Tags removed: verification-needed-jammy-linux-oem-6.1
** Tags added: verification-done-jammy-linux-oem-6.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2042912
Title:
Public bug reported:
back-out zstd module compression automatic for backports
we decided to have kernel modules zstd compressed in mantic+, and keep
them uncompressed in jammy backports.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- back zstd
** Tags removed: verification-needed-lunar-linux-kvm
** Tags added: verification-done-lunar-linux-kvm
--
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/2042546
Title:
Include cifs.ko in
Failing build had kernel
Kernel version: Linux bos03-riscv64-014 5.19.0-1021-generic
#23~22.04.1-Ubuntu SMP Thu Jun 22 12:49:35 UTC 2023 riscv64
The build immediately before the first failure had kernel
Kernel version: Linux riscv64-qemu-lgw01-069 5.13.0-1019-generic
#21~20.04.1-Ubuntu SMP Thu
November 16 was 2 days after livecd-rootfs 24.04.4 landed in the noble
release pocket, superseding 24.04.2.
The code delta between 24.04.2 and 24.04.4 includes removal of support
for "legacy" images (SUBPROJECT=legacy) which doesn't apply here; and
some reorganization of code related to
Public bug reported:
In mantic, we migrated livecd-rootfs to use losetup -P instead of
kpartx, with the expectation that this would give us a reliable, race-
free way of loop-mounting partitions from a disk image during image
build.
In noble, we are finding that it is no longer reliable, and in
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
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/2039575
Title:
SMC stats: Wrong bucket calculation for payload of exactly 4096
I wondered why my old bug report has not gotten any attention. Being a
duplicate of this bug didn't help, but at least someone from the
security team marked it as a duplicate of this bug.
BUT... On Bug Reports filed against zfs-linux, there are 55 bugs, with
not one single person assigned, that
Public bug reported:
I am using UBUNTU 23.10 with Vega 64 using the latest amdgpu drivers.
This started when I upgraded to 23.10. Was not happening in 22.04 or
23.04.
In Wayland, it always crashes the gnome session and I have to hardware
power off the system. It also sometimes makes a weird
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-aws-6.2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-aws-6.2 in Ubuntu.
@AMD, any idea about the above?
--
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/2045573
Title:
AMDGPU: cp queue preemption timeout
Status in linux package in Ubuntu:
New
Bug
This will be fixed by this patch:
https://lore.kernel.org/amd-
gfx/20231201005751.4194154-1-jiadong@amd.com/
Until Canonical pulls it in for now you can use amdgpu.mcbp=0 on kernel
command line to avoid it.
--
You received this bug notification because you are a member of Kernel
Packages,
I'm not sure if this has been really fixed in Jammy default kernel. I've
hit specifically this issue during this week while running 5.15.0-89.
Upgrading to HWE kernel or 5.19.0-50 does fix live migrations.
--
You received this bug notification because you are a member of Kernel
Packages, which
This is my merge fo a Bug Report marked as a duplicate of this one:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2044969
In the OpenZFS patch thread, they had said that feature@block_cloning,
because of the underlying bug, OpenZFS had said they turned that feature
off by default in
Public bug reported:
Happened on Lenovo T14 AMD gen 2 5850U running Mantic 6.5.0-13-generic
Under load, GPU crashed resulting in a weird behavior. Screen froze,
blinked a few times and the laptop suspended. After wakeup a normal
login screen showed up but after logging in, it crashed to black
Same here...none of these commands remove the old /lib/modules/ kernel
dirs:
sudo apt-get clean
sudo apt-get autoclean
sudo apt-get autoremove
sudo apt-get purge
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
I have tried this (patches suggested in comment #40) and the problem
seems to have gone away. It may be too soon to say but my test scenario
(which never gave me a false negative before) finished without issues.
Of course this is not a 'fix', so I'm curious to see what the OP has to
say about
I don't believe so, I'm on one of the affected laptops on
6.2.0-37-generic / 23.04 with no issues. It's 23.10's kernel 6.5 that
triggers the issue for me. The bug is also about 23.10, which wouldn't
have kernel 6.2 anyway.
--
You received this bug notification because you are a member of Kernel
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed
@copong
> I'm not sure why kernel 6.2 keeps getting suggested by the ubuntu bot, it's
> never been affected by this bug, at least not on any kernel packaged for
> ubuntu 23.04.
Maybe the bug had been backported?
--
You received this bug notification because you are a member of Kernel
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1
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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1
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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1
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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1
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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1
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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1
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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2041495
Title:
Could
** Changed in: linux-nvidia-6.2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2042697
Title:
Pull request to address thermal core
That was already CC to stable, so I suggest checking the latest 5.15.y.
If that's still not working, you probably need
https://github.com/torvalds/linux/commit/2757a848cb0f184850d3e0a33b4a69e8014fdc5d
backported too.
--
You received this bug notification because you are a member of Kernel
It's probably a duplicate of the same patches missing for bug 2036742.
https://github.com/torvalds/linux/commit/64ffd2f1d00c6235dabe9704bbb0d9ce3e28147f
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
All autopkgtests for the newly accepted linux-meta-hwe-6.2
(6.2.0.39.40~22.04.16) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
backport-iwlwifi-dkms/9858-0ubuntu3.4 (armhf)
Please visit the excuses page listed below and
** Description changed:
+ SRU Justification:
+
+ [Impact]
+
Debian source format 1.0 cannot remove files, create symlinks and change
permission in the .diff.gz tarball. Therefore any changes in these 3
categories cannot be represented without any tricks. To solve this,
the `reconstruct`
** Tags removed: verification-needed-lunar-linux-aws
verification-needed-lunar-linux-azure
** Tags added: verification-done-lunar-linux-aws
verification-done-lunar-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Tags removed: verification-done-mantic
** Tags added: verification-done-mantic-linux
--
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/2042850
Title:
Boot log print hang on screen, no
Public bug reported:
Debian source format 1.0 cannot remove files, create symlinks and change
permission in the .diff.gz tarball. Therefore any changes in these 3
categories cannot be represented without any tricks. To solve this,
the `reconstruct` script is used every time we build the source
I'm not sure why kernel 6.2 keeps getting suggested by the ubuntu bot,
it's never been affected by this bug, at least not on any kernel
packaged for ubuntu 23.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@arighi I created another bug for this because it is a general issue, not only
for this `is_rust_module.sh` script.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045562
The command `rm -f` should stay because in v6.5 the script is still there, and
in debian 1.0 we don't properly
AFAIU by default it's unattended-upgrades that takes care of removing
old kernel (and kernel module packages). Apparently it doesn't pass
--purge when it removes the old kernel packages. Should it?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
SRU Justification
[Impact]
The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops
VMs using these kernels from being configurable using qemu or cloud-
hypervisor's SMBIOS type 11 strings. This feature is supported and used
widely by systemd:
This bug is awaiting verification that the linux-gcp/6.2.0-1020.22
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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the
Public bug reported:
Hello!
We have Ubuntu OS-based servers running in both AWS and Azure clouds.
These servers are handling thousands of connections, and we've been
experiencing issues with TCP memory usage since upgrading to Ubuntu
22.04.3 from 22.04.2.
$ cat /proc/net/sockstat
sockets:
This bug is awaiting verification that the linux-aws/6.2.0-1017.17
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-lunar-linux-aws' to 'verification-done-lunar-
linux-aws'. If the
This bug is awaiting verification that the linux-lowlatency-
hwe-6.2/6.2.0-1018.18~22.04.1 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-jammy-linux-
lowlatency-hwe-6.2' to
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.04.1 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-jammy-linux-
hwe-6.2' to
This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If
This bug is awaiting verification that the linux-starfive/6.2.0-1010.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-lunar-linux-starfive' to 'verification-done-
This bug is awaiting verification that the linux-kvm/6.2.0-1018.18
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-lunar-linux-kvm' to 'verification-done-lunar-
linux-kvm'. If the
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.04.1 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-jammy-linux-
hwe-6.2' to
This bug is awaiting verification that the linux-gcp/6.2.0-1020.22
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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the
This bug is awaiting verification that the linux-starfive/6.2.0-1010.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-lunar-linux-starfive' to 'verification-done-
This bug is awaiting verification that the linux-gcp/6.2.0-1020.22
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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the
This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.04.1 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-jammy-linux-
hwe-6.2' to
This bug is awaiting verification that the linux-aws/6.2.0-1017.17
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-lunar-linux-aws' to 'verification-done-lunar-
linux-aws'. If the
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.04.1 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-jammy-linux-
hwe-6.2' to
This bug is awaiting verification that the linux-aws/6.2.0-1017.17
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-lunar-linux-aws' to 'verification-done-lunar-
linux-aws'. If the
This bug is awaiting verification that the linux-kvm/6.2.0-1018.18
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-lunar-linux-kvm' to 'verification-done-lunar-
linux-kvm'. If the
This bug is awaiting verification that the linux-lowlatency-
hwe-6.2/6.2.0-1018.18~22.04.1 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-jammy-linux-
lowlatency-hwe-6.2' to
This bug is awaiting verification that the linux-gcp/6.2.0-1020.22
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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the
This bug is awaiting verification that the linux-starfive/6.2.0-1010.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-lunar-linux-starfive' to 'verification-done-
This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If
This bug is awaiting verification that the linux-lowlatency-
hwe-6.2/6.2.0-1018.18~22.04.1 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-jammy-linux-
lowlatency-hwe-6.2' to
This bug is awaiting verification that the linux-starfive/6.2.0-1010.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-lunar-linux-starfive' to 'verification-done-
This bug is awaiting verification that the linux-aws/6.2.0-1017.17
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-lunar-linux-aws' to 'verification-done-lunar-
linux-aws'. If the
This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If
This bug is awaiting verification that the linux-gcp/6.2.0-1020.22
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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the
This bug is awaiting verification that the linux-kvm/6.2.0-1018.18
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-lunar-linux-kvm' to 'verification-done-lunar-
linux-kvm'. If the
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.04.1 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-jammy-linux-
hwe-6.2' to
This bug is awaiting verification that the linux-lowlatency-
hwe-6.2/6.2.0-1018.18~22.04.1 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-jammy-linux-
lowlatency-hwe-6.2' to
This bug is awaiting verification that the linux-starfive/6.2.0-1010.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-lunar-linux-starfive' to 'verification-done-
1 - 100 of 140 matches
Mail list logo
