Alright, there's no need to wait for a fix here. Mainly because there's
no one to verify a fix anymore.
** No longer affects: bluez (Ubuntu Jammy)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Also affects: linux-hwe-5.19 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.19 (Ubuntu)
Status: New => Confirmed
** Changed in: linux-hwe-5.19 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1969959 ***
https://bugs.launchpad.net/bugs/1969959
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1969959, so it is being marked as such. Please
You have been subscribed to a public bug:
using the "try ubuntu" feature, this is what the entire experience looks
like (see the 2nd attached image in comment #2).
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic
https://lists.ubuntu.com/archives/kernel-team/2023-April/138657.html
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.1 (Ubuntu)
Importance:
** Description changed:
- [Impact]
+ [Impact]
(Cpoied from commit message)
Usage of `set -e` before executing a command causes immediate exit
on failure, without cleanup up the resources allocated at setup.
This can affect the next tests that use the same resources,
leading to a chain
Yeah I was wrong too. Each time I thought a kernel update or even
monitor firmware update fixed it, my problem came back eventually. Seems
to be related to how good my USB-C connection is. Even confirmed the
same problem on a second identical monitor, and with multiple different
cables.
Overall
*** This bug is a duplicate of bug 1998244 ***
https://bugs.launchpad.net/bugs/1998244
This issue has been fixed in bug 1998244
** This bug has been marked a duplicate of bug 1998244
kselftest net/fib_nexthop_nongw.sh fails
--
You received this bug notification because you are a member
** Tags added: amd oem-priority
--
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 HWE Next:
New
** Summary changed:
- [nvidia] gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid
parameter attributes)'. (Details: serial error_code 8 request_code 131
(XInputExtension) minor_code 57)]
+ gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
This bug was fixed in the package linux-riscv - 6.2.0-19.19.1
---
linux-riscv (6.2.0-19.19.1) lunar; urgency=medium
* lunar/linux-riscv: 6.2.0-19.19.1 -proposed tracker (LP: #2013348)
* Enable StarFive VisionFive 2 board (LP: #2013232)
- net: phy: motorcomm: change the phy
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/2015924
Title:
package
Public bug reported:
error while installing linux-image-6.2.0-20-generic
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-20-generic 6.2.0-20.20
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.15
(5.15.0-1032.40~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)
Please visit the
All autopkgtests for the newly accepted linux-restricted-modules-nvidia-5.19
(5.19.0-1009.9+3) 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
Still same problem with new kernel 6.2.0-20-generic
--
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/2015670
Title:
Kernel loop PCIe Bus Error on RTL810xE
Status in linux package in
** Description changed:
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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-
nvidia-5.19/5.19.0-1009.9 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
This bug is awaiting verification that the linux-gke/5.4.0-1097.104
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,
This bug is awaiting verification that the linux-
gcp-4.15/4.15.0-1148.164 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
This bug is awaiting verification that the linux-
gke-5.15/5.15.0-1031.36~20.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-focal' to
'verification-done-focal'. If the problem
All autopkgtests for the newly accepted linux-meta-azure-fde-5.15
(5.15.0.1036.43~20.04.1.15) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
The verification of the Stable Release Update for systemd 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 event that you encounter a
This bug was fixed in the package systemd - 245.4-4ubuntu3.21
---
systemd (245.4-4ubuntu3.21) focal; urgency=medium
* udev: avoid NIC renaming race with kernel (LP: #2002445)
Files:
-
debian/patches/lp2002445-netlink-do-not-fail-when-new-interface-name-is-already-us.patch
The verification of the Stable Release Update for systemd 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 event that you encounter a
This bug was fixed in the package systemd - 245.4-4ubuntu3.21
---
systemd (245.4-4ubuntu3.21) focal; urgency=medium
* udev: avoid NIC renaming race with kernel (LP: #2002445)
Files:
-
debian/patches/lp2002445-netlink-do-not-fail-when-new-interface-name-is-already-us.patch
** Summary changed:
- Focal update: upstream stable patchset 2023-04-11
+ Focal update: v5.4.233 upstream stable release
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope
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
These are the size of linux-kvm debs at the time of this writing[1]:
linux-buildinfo-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb (397.9 KiB)
linux-headers-6.2.0-1003-kvm_6.2.0-1003.3_amd64.deb (15.9 MiB)
linux-image-unsigned-6.2.0-1003-kvm-dbgsym_6.2.0-1003.3_amd64.ddeb (203.2
MiB)
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Roxana Nicolescu (roxanan)
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a
This is ran on daily images, the kernel versions are already listed above.
Hence no need to ran apport-collect for this issue.
Setting to "Confirmed"
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
This bug is awaiting verification that the linux-gkeop/5.4.0-1067.71
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,
Carlos, if this is still an issue then please provide requested
information otherwise this bug report will either expire or be made
invalid.
** Tags added: lunar
** Package changed: ubuntu => steam (Ubuntu)
** Changed in: steam (Ubuntu)
Status: New => Incomplete
--
You received this
All autopkgtests for the newly accepted linux-restricted-modules-oem-5.17
(5.17.0-1030.31+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
** Summary changed:
- Power guest secure boot with static keys: kernel portion
+ [24.04] Power guest secure boot with static keys: kernel portion
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Everyone!
Found the same bug on my system:
Host: Ubuntu 22.04.02, kernel 5.15, Ryzen 5950x
Hypervisor: KVM
VM: ESXi 7.0u3
ESXi works fine and I'm able to start VMs on it (nested virtualization)
After updating the kernel to 5.19 or 6.0-oem I get this error anytime I try to
start a VM on the
Public bug reported:
This was observed on:
- focal:linux-hwe-5.15
- cycle 20230320
- rumford
Logs:
18690 05:38:38 DEBUG| memcg_usage_in_bytes_test 1 TINFO: timeout per
run is 0h 5m 0s
18691 05:38:38 DEBUG| memcg_usage_in_bytes_test 1
TINFO: set
You are right. That's it. Please try -proposed kernel and write about your
testing results.
Feel free to reach me on the forum/IRC if you have any questions.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi, I do think I'm affected by the same issue. Is it still helpful to
test the 5.19.0-40.41 kernel as proposed by the kernel bot in the
previous message? I don't want to mess up my server, but if it helps
getting this fixed faster for 22.04, I'm willing to install the kernel
from -proposed.
This failed in cycle 20230320 for focal:linux-hwe-5.15
Running tests...
Name: cpuhotplug04
Date: Tue Apr 11 05:47:01 UTC 2023
Desc: Does it prevent us from offlining the last CPU?
/opt/ltp/testcases/bin/cpuhotplug04.sh: 99: echo: echo: I/O error
cpuhotplug04 1 TFAIL: Could not offline
This affects focal:linux-hwe-5.15. I've encountered it in the 20230320
cycle.
** Also affects: linux-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-hwe-5.15 (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification
This bug is awaiting verification that the linux-ibm/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
Same issue as LP: #2011748, that should be fixed by: a6d8a9c1e5fa
("arm64: efi: Use SMBIOS processor version to key off Ampere quirk")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
- Issue found on 6.2.0-20.20 ARM64 instances.
+ Issue found on 6.2.0-20.20 ARM64 instances "dazzle" only.
- Looks like the memfd:run_fuse_test.sh will never finish properly and the
+ Looks like the efivarfs:efivarfs.sh will never finish properly and the
whole test
It worked like a charm, @giuliano69
After modifying said line, i compiled and installed, and then ran "sudo rmmod
uvcvideo && sudo modprobe uvcvideo" as said in #24, and boom.
I`ll do my part and share this solution on every other page where i`ve
seen this problem reported.
Thanks for the help
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 2015867
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Hi,
in the regular monitoring of metrics there was a bump in disk size last week.
The default image once installed consumes now 994 (formerly 859) megabytes.
Looking at the consumers there was much noise, but the biggest change
was
linux-headers-5.19.0-1008-kvm 25197 ->
I found this issue is limited to node "dazzle", other ARM64 nodes like
kopter-kernel and scobee-kernel they do not have this issue.
Also, a manual test show the real cause seems to be the efivarfs.sh in
efivarfs, which can be found failed with timeout in the RT test report.
Running the test
** Changed in: linux-bluefield (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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2012571
Title:
net/sched: cls_api:
** Changed in: linux-bluefield (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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2013422
Title:
net: sched: allow
** Changed in: linux-bluefield (Ubuntu Focal)
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/2015293
Title:
netfilter: ctnetlink: Support
** Changed in: linux-bluefield (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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2013758
Title:
Add support for
** Changed in: linux-bluefield (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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2015515
Title:
net: sched: allow
I can confirm that this issue does not exist in L / L-lowlatency.
Hints removed.
** Changed in: ubuntu-kernel-tests
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member
Hi @chengendu,
Thanks.
I have posted a comment to the effect of backporting changes in new (and
at the time, unreleased and not yet stable) Linux kernels to LTS
releases. There is no need to await upstream's feedback and judgment,
this change belongs to Linux 6.2, not old LTS kernels.
--
You
Please note that this is a bug that for unknown reasons have been
backported from 6.2-rc3 to LTS released kernels in Ubuntu Server LTS.
Upstream is not responsible for making the decision of whether this
backported change should be part of older kernels in Ubuntu Server LTS.
Please revert the
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 2015855
and then change the status of the bug to 'Confirmed'.
If, due to the
Waiting on intel response if these 2 commits
- b041b525dab95
- 727209376f499
are needed to support this as well.
--
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/2015855
Title:
Add split
Public bug reported:
SRU Justification
[Impact]
#2009315 adds support for their new Emerald Rapids CPU to Jammy.
Commit d7ce15e1d4162ab5e56dead10d4ae69a6b5c8ee8 from linux-next
introduces support for Split lock detection.
[Testing]
Kernel was built on cbd and boot tested on a VM.
TODO ask
This bug was fixed in the package linux - 6.2.0-20.20
---
linux (6.2.0-20.20) lunar; urgency=medium
* lunar/linux: 6.2.0-20.20 -proposed tracker (LP: #2015429)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/master)
* FTBFS
This bug was fixed in the package linux - 6.2.0-20.20
---
linux (6.2.0-20.20) lunar; urgency=medium
* lunar/linux: 6.2.0-20.20 -proposed tracker (LP: #2015429)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/master)
* FTBFS
This bug was fixed in the package linux - 6.2.0-20.20
---
linux (6.2.0-20.20) lunar; urgency=medium
* lunar/linux: 6.2.0-20.20 -proposed tracker (LP: #2015429)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/master)
* FTBFS
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules-hwe-5.19 in
Ubuntu.
https://bugs.launchpad.net/bugs/2015846
Title:
package linux-modules-nvidia-470-5.19.0-38-generic
Public bug reported:
impossible to resolve driver nvidia gtx3060 for ubuntu 20.04
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-modules-nvidia-470-5.19.0-38-generic 5.19.0-38.39~22.04.1+1
ProcVersionSignature: Ubuntu 5.19.0-38.39~22.04.1-generic 5.19.17
Uname: Linux
I can see this test being tested with K-aws / K-azure.
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
linux-firmware SRU:
* https://lists.ubuntu.com/archives/kernel-team/2023-April/138627.html (jammy)
* https://lists.ubuntu.com/archives/kernel-team/2023-April/138628.html (lunar)
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu
Well, you camera model is 0408:4033, so it is NOT 0408:4035
So it will bot be recognized by the uvc driver... You could try to download and
modify
https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User-Facing-0x0408-0x4035-/blob/main/uvc_driver.c
al line 2676, and changing the line
DCN 3.1.4 is not supported by Kinetic kernel v5.19. Marking as INVALID.
** Changed in: linux-firmware (Ubuntu Kinetic)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 105 matches
Mail list logo
