Like everyone else, I've had this for a while...
AMD Radeon™ RX 6600 XT
but it seems
5.19.0-32
isn't available
--
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/2009136
Title:
No HDMI aud
Hi Alberto & Andy,
Currently our customer met this issue on focal too.
We released image with 5.14.0-1032.35 oem kernel and nvidia
510.51-0ubuntu0.20.04.1, and the unattended-upgrade upgraded to 5.14.0-1051.58,
and the nvidia modules could not be installed.
Could you help apply the jammy's f
** Also affects: linux-meta-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1997505
Title:
Unattended-Upgrade w
** Tags added: jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1766857
Title:
[Hyper-V] KVP daemon fails to start
Status in linux package in Ubuntu:
Confirmed
Status in lin
I'm seeing the problem with /usr/libexec/hypervkvpd being used by
hv_kvp_daemon, when the scripts are in /usr/sbin on a newly created
Ubuntu 22.04 VM (on Windows 11 Pro 22H2 Hyper-V), on the linux-azure
kernel.
murph@Ubuntu-Virtual-Machine:~$ uname -a
Linux Ubuntu-Virtual-Machine 5.15.0-1035-azure
This bug is awaiting verification that the linux-ibm/5.15.0-1028.31
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' to 'verification-done-jammy'. If the
problem still exists, ch
All autopkgtests for the newly accepted linux-meta-oem-5.17 (5.17.0.1030.28)
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
dahdi-linux/1:2.11.1~dfsg-1ubuntu12~22.04.1 (amd64)
Please visit the excuses page listed below and invest
This bug was fixed in the package nvidia-graphics-drivers-525 -
525.105.17-0ubuntu1
---
nvidia-graphics-drivers-525 (525.105.17-0ubuntu1) lunar; urgency=medium
* New upstream release (LP: #2012529).
-- Alberto Milone Mon, 27 Mar 2023
11:29:08 +
** Changed in: nvidia-graphic
This bug was fixed in the package nvidia-graphics-drivers-525 -
525.105.17-0ubuntu1
---
nvidia-graphics-drivers-525 (525.105.17-0ubuntu1) lunar; urgency=medium
* New upstream release (LP: #2012529).
-- Alberto Milone Mon, 27 Mar 2023
11:29:08 +
** Changed in: nvidia-graphic
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/2008823
Title:
/sys/kernel/boot_params/data leaks random data
Status
This bug is awaiting verification that the linux-raspi2/4.15.0-1130.138
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-bionic' to 'verification-done-bionic'. If the
problem still exis
This bug is awaiting verification that the linux-oracle/4.15.0-1117.128
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-bionic' to 'verification-done-bionic'. If the
problem still exis
This bug is awaiting verification that the linux-gcp/5.19.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-kinetic' to 'verification-done-kinetic'. If the
problem still exists
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/2015414
Title:
5.15.0-69 ice driver deadlocks
This bug is awaiting verification that the linux-ibm/5.4.0-1047.52
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, cha
Public bug reported:
The ice driver in the 5.15.0-69 kernel deadlocks on rtnl_lock() when
adding e810 NICs to a bond interface. Booting with
`sysctl.hung_task_panic=1` and `sysctl.hung_task_all_cpu_backtrace=1`
added to the kernel command-line shows (among lots of other output):
```
[ 244.98010
All autopkgtests for the newly accepted linux-restricted-modules-oracle
(5.19.0-1020.23) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)
Please visit the excuses page l
*** This bug is a duplicate of bug 1893956 ***
https://bugs.launchpad.net/bugs/1893956
H Valerie / Jeff,
Are you still in certification submission review team ?.
I have one system model ready to submit for the review.
Somehow the used link does not work now .
Would you please provide me th
This bug is awaiting verification that the linux-gkeop/5.15.0-1018.23
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-gkeop/5.15.0-1018.23
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' to 'verification-done-jammy'. If the
problem still exists,
All autopkgtests for the newly accepted linux-restricted-modules-nvidia
(5.15.0-1018.18+1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page l
All autopkgtests for the newly accepted linux-restricted-modules-gcp
(5.19.0-1020.22) for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)
Please visit the excuses page list
This bug is awaiting verification that the linux-oracle/5.19.0-1020.23
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-kinetic' to 'verification-done-kinetic'. If the
problem still exi
** Changed in: linux-oracle-5.15 (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2011854
Title:
cmos_interrupt not
Cuda testing passed for all drivers (470, 515, 525, 450-server,
470-server, 515-server, 525-server) on bionic, focal, jammy and kinetic
using both DKMS and LRM (when using the appropriate stream 2 ppa for the
LRM packages). DKMS testing also passed on lunar.
--
You received this bug notification
** Tags added: kernel-bug
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2015400
Title:
losetup with mknod fails on jammy with kernel 5.15.0-69-generic
Status in linux package
** Also affects: linux-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New
** Tags added: jammy
--
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/2015400
Title:
losetup with mkno
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/2015400
Public bug reported:
losetup fails with devices created manually by mknod on kernel
5.15.0-69-generic
# fallocate -l 1G test
# mknod -m 660 /dev/loop8 b 7 8
# chown root:disk /dev/loop8
# losetup /dev/loop8 ./test
losetup: ./test: failed to set up loop device: Device or resource busy
Possibly as
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661371/+files/acpidump.txt
--
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/20
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661370/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661369/+files/UdevDb.txt
--
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/2008823
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661368/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661367/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661366/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661365/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661364/+files/Lsusb-v.txt
--
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/2008
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661363/+files/Lspci-vt.txt
--
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/20
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661362/+files/Lspci.txt
--
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/2008823
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2008823/+attachment/5661361/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Tags added: apport-collected staging
** Description changed:
Looking at /sys/kernel/boot_params/data I see that much of the 4096 byte
buffer is old kernel data.
It really stood out as I saw parts of email contents in there.
It seems b
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
You have been subscribed to a public bug:
losetup fails with devices created manually by mknod on kernel
5.15.0-69-generic
# fallocate -l 1G test
# mknod -m 660 /dev/loop8 b 7 8
# chown root:disk /dev/loop8
# losetup /dev/loop8 ./test
losetup: ./test: failed to set up loop device: Device or resou
You have been subscribed to a public bug:
losetup fails with devices created manually by mknod on kernel
5.15.0-69-generic
# fallocate -l 1G test
# mknod -m 660 /dev/loop8 b 7 8
# chown root:disk /dev/loop8
# losetup /dev/loop8 ./test
losetup: ./test: failed to set up loop device: Device or resou
I tested this same scenario on Ubuntu 22.04.2 and while I still don't
have a wireless device available I did discover the following:
bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ ubuntu-drivers list
bcmwl-kernel-source
bdmurray@bdmurray-Standard-PC-Q35-ICH9-2009:~$ ubuntu-drivers devices
== /sys/
Public bug reported:
Hi,
Lunar, 525.105.17
I get a very very very slow boot using dynamic graphics in my Lenovo Legion 5i
pro i7/3070 Ti.
Using discrete graphics is ok.
Using Nouveau with hybrid graphics is ok.
After some research, it seems the culprit is:
Failed to start systemd-backlight@ba
This bug is awaiting verification that the linux-raspi/5.15.0-1027.29
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-raspi/5.4.0-1083.94
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, c
I tried installing using the desktop legacy image and noticed that
`ubuntu-drivers` behaves the same way - recommending broadcom-sta-dkms
but then not installing it. Additionally, looking at the device I see
the following (which I also recall from the new installer):
05:00.0 Network controller [02
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 2008823
and then change the status of the bug to 'Confirmed'.
If, due to the nature
After installing with the new desktop installer, rebooting, manually
installing broadcom-sta-dkms, and rebooting again no wireless adapter
was available.
Additionally, running 'ubuntu-drivers install' (before installing
broadcom-sta-dkms) indicated that all drivers were already installed.
--
You
** Package changed: linux-signed-hwe-5.19 (Ubuntu) => linux (Ubuntu)
--
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/2008823
Title:
/sys/kernel/boot_params/data leaks random data
Status
Oh yes, an ec2 instance I have that has non-zero content at the end of
the file:
Linux ip-172-26-15-115 4.4.0-1154-aws #169-Ubuntu SMP Fri Feb 17
11:05:27 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
This bug is awaiting verification that the linux-kvm/4.15.0-1138.143
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-bionic' to 'verification-done-bionic'. If the
problem still exists,
** Changed in: linux-azure (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Jammy)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu Kinetic)
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure
Public bug reported:
TODO current status in lunar and mainline.
The following commits had to be backported to Jammy:
Usually backporting new features to existing kernels it's not a common practice.
But these backports were easy to pick. Some of the commits were already applied.
More information
** Changed in: hwe-next
Status: New => Fix Released
--
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/2008217
Title:
Unsolicited wake from suspend with bluetooth connected (
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1998883
Title:
Micron NVME storage failure [1344,5407]
Status in HWE N
Public bug reported:
SRU Justification
[Impact]
Microsoft has requested the inclusion of commit
88e378d400fa0544d51cf62037e7774d8a4b4379 ('x86/ioremap: Add hypervisor
callback for private MMIO mapping in coco VM') from linux-next.
[Regression Potential]
Private memory mappings could be incorre
are you sure the dkms module is still needed with the v6.2 kernel?
--
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/2013236
Title:
Failed to install bcmwl wireless driver during t
This bug was fixed in the package v4l2loopback - 0.12.7-2ubuntu3
---
v4l2loopback (0.12.7-2ubuntu3) lunar; urgency=medium
* Revert to 0.12.7-2ubuntu1, as dkms that unconditionaly exports CC has
been reverted. Otherwise, currently src:linux FTBFS when trying to
vendor in this
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 2015361
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
build_dkms fails
1) if updated dkms is used that changes return code for skip from 9 to 77
2) if MAKEFLAGS are exported that remove implicit variables, which dkms module
submake invocations may require
fix those things for lunar release.
** Affects: linux (Ubuntu)
Imp
** Tags removed: block-proposed-lunar
** Changed in: v4l2loopback (Ubuntu)
Status: New => 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/2015279
Title:
ftbfs during
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/1971151
Title:
[SRU][Ubuntu 22.04.1] mpi3mr: Add manageme
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 2015352
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** No longer affects: linux (Ubuntu)
** Changed in: linux-firmware (Ubuntu)
Status: Triaged => Fix Released
--
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/1523565
Title:
Public bug reported:
Description:
On a Dell EMC PE system configured with Intel E810 card installed with Ubuntu
22.04.2.
When bonding is enabled on the server, the system will hang at the
initialization of OS.
The kernel loads, but the system hang around the time it starts the Network
Service
Oh man. This turned out to be a hardware issue. A replacement adapter
works fine. I'd never have thought, when the kernel changed so much.
I'm on 5.19 now, didn't see a glitch yet, where I'd normally couldn't
work.
Phew.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You
broken pipe error 32 linux firmware and linux kernel
--
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/2015223
Title:
linux-firmware logs kernel
Status in linux-firmware package i
** Also affects: linux-bluefield (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/2015293
Title:
netfilter: ctnetlink:
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
--
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/2015307
Title:
mmc: sdhci-of-dwcmshc:
** Tags added: kern-6380
--
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/2015139
Title:
package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to
install/upgrade: não p
** Tags added: kern-6379
--
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/2015139
Title:
package linux-firmware 20220329.git681281e4-0ubuntu3.10 failed to
install/upgrade: não p
dpkg-deb (sub-processo): ZSTD_decompressStream error : Corrupted block
detected
--
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/2015139
Title:
package linux-firmware 20220329.git
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 2015308
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Details will be provided later via comments.
==> Please mark this LP entry as "private"
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 bugnameltc-202168 seve
You have been subscribed to a public bug:
Details will be provided later via comments.
==> Please mark this LP entry as "private"
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Tags: architecture-s39064 b
That bug description is not very helpful. Please explain what you think
is your problem and why you think it's firmware related.
** Tags added: kern-6371
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bu
That bug description is not very helpful. Please explain what you think
is your problem and why you think it's firmware related.
** Tags added: kern-6372
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bu
** Tags added: kern-6373
--
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/2015297
Title:
Update GPU F/W for DCN 3.1.4 products to fix S0i3 issue
Status in linux-firmware package
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/2015308
Title:
Amd Radeon Navi RX 6600m poor performance
Statu
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 2015279
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Description changed:
ftbfs during kernel build due to dkms changes in lunar
need to revert explicit use of CC= variable, which is now no longer
guaranteed to be exported once again.
causes src:linux to FTBFS
+
+
+ --
+
+ dkms in jammy and lunar are incompatible with each other,
** Changed in: ubuntu-kernel-tests
Status: In Progress => 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/2004644
Title:
Incompatible jbd2 format between kernel and lt
** Changed in: autopkgtest (Ubuntu Jammy)
Status: New => Invalid
** Changed in: autopkgtest (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-kvm (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-kvm (Ubuntu Kinetic)
Status: New => Invalid
--
You
new kernel 5.19.0-1023-aws fixed the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1989470
Title:
BGP adjacency not established on linux-image-5.15.0-1019-aws
Status in linu
This bug is not related to bluefield, hence setting focal verification
again to done, to unblock.
--
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/1999882
Title:
[UBUNTU 20.04] KVM: s390:
Same problem, 67 -> wifi works, 69 -> wifi disapears.
wireless card is ASUS PCE-AC88
Some digging supports theory that patch was backported to kernel
5.15.0-69 which treats valid value as faulty/indication of error
therefore preventing loading of module:
[ 2740.647600] brcmfmac :0d:00.0: brc
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66
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 exist
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66
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 exist
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66
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 exist
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66
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 exist
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66
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 exist
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66
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 exist
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66
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 exist
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66
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 exist
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66
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 exist
This bug is awaiting verification that the linux-bluefield/5.4.0-1060.66
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 exist
1 - 100 of 108 matches
Mail list logo
