** Changed in: firmware-sof (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to firmware-sof in Ubuntu.
https://bugs.launchpad.net/bugs/1992714
Title:
[SRU] SoF for RPL platform support
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to firmware-sof in Ubuntu.
https://bugs.launchpad.net/bugs/1992714
** Changed in: linux-xilinx-zynqmp (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu.
https://bugs.launchpad.net/bugs/1992912
Title:
Still happens in 5.15.0-53.
--
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/1995903
Title:
Can't boot with kernel 5.15.0-52
Status in linux package in Ubuntu:
Confirmed
Bug
** Also affects: linux-xilinx-zynqmp (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu.
https://bugs.launchpad.net/bugs/1992912
Title:
The audio works with the 6.0-oem kernel built from the latest git tree
which includes -1007 and stable update 6.0.4, 6.0.5, 6.0.6, and 6.0.7
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to firmware-sof in Ubuntu.
I suspect there are more kernels that cause instability with this NVME
device (don't know whether it is the hardware or the kernel the
culprit).
Using kernels 5.15.0-50 and 5.15.0-43 made the system less unstable than
the reported kernel (5.15.0-52), the nvme0 power-off message did not
show up,
Did you ever end up testing your own patch for that other drive?
--
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/1970136
Title:
Optical drive no longer usable after upgrading to kernel
Great news!!! Got the new machine. Avoided booting into windows, ever,
just in case. Executed your steps 1 through 8 (except for the
default.pa part... I wasn't sure if that was crucial, and figured I'd
save it until it seemed needed). Boot fresh machine, no sound. Apply
the verbs - The other
So why is this not yet reverted? I see that 5.15.0-53 is now available,
should I even bother updating my kernel at all now? I cannot
risk the stability of my system with this broken code.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Also affects: linux-xilinx-zynqmp (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-xilinx-zynqmp (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
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
I will process mainline kernel testing.
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Taihsiang Ho (taihsiangho)
--
You received this bug notification because you are a member of Kernel
Packages, which is
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 1996547
and then change the status of the bug to 'Confirmed'.
If, due to the
** Package changed: 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/1996547
Title:
integrated Webcam not working Ubuntu 22 Kernel 5.15
Status in linux:
New
You have been subscribed to a public bug:
Getting the following error while trying to use the webcam
uvcvideo 1-6:1.1: Failed to resubmit video URB (-19)
dmesg | grep video
sudo dmesg | grep video
[ 41.778881] videodev: Linux video capture interface: v2.00
[ 42.298170] ACPI: video: Video
Thanks! OK, that shows that we've successfully booted the kernel, but it
is having an issue bringing up a CPU. I've pasted the relevant snippet
below. It isn't obvious to me if this is a kernel issue or some other
platform issue. As a next step, I'd suggest attempting to reproduce w/
the latest
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-azure-4.15 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects:
b064edad2c46ef8e16b7e42ae9bc14bbeb30bb82 is the first bad commit
commit b064edad2c46ef8e16b7e42ae9bc14bbeb30bb82
Author: Richard Gobert
Date: Mon Aug 29 13:18:51 2022 +0200
net-next: Fix IP_UNICAST_IF option behavior for connected sockets
--
You received this bug notification because you
Here is the log that reproduce the hang.
** Attachment added: "papat.log"
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+attachment/5630877/+files/papat.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
This bug is awaiting verification that the linux/5.15.0-54.60 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, change
Yes, thank you for the brightness fix.
If it helps, I did remember the changes to make to the common.c file for
logging. In that bsd article you can ignore most of the text, but
somewhere in the middleish there is a hyper link that says something
like my hack. If you click on it, it shows you
We won't SRU bug 1975573, therefore iwlmei is not built in Jammy.
** Changed in: backport-iwlwifi-dkms (Ubuntu Jammy)
Status: Confirmed => Won't Fix
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
We have no longer the case that two compat.ko might be installed at the
same time.
** Changed in: backport-iwlwifi-dkms (Ubuntu Jammy)
Status: In Progress => Won't Fix
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: In Progress => Won't Fix
--
You received this bug
Seeing this too, on kinetic, it happens during suspend.. on
5.19.0-23-generic #24-Ubuntu
Nov 15 18:05:17 -XPS-15-7590 kernel: [15509.799535] Freezing remaining
freezable tasks ... (elapsed 0.001 seconds) done.
Nov 15 18:05:17 -XPS-15-7590 kernel: [15509.800992] printk: Suspending
console(s)
I think this might be related:
journalctl -p 3 -xb
nov 15 12:53:55 cinnamon systemd-udevd[643]: event6: Failed to call
EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
sudo cat /proc/bus/input/devices | grep -C 5 event6
I: Bus=0019 Vendor= Product= Version=
N:
** Tags added: lookout-canyon oem-priority originate-from-1962102
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/1996611
Title:
CPU/Memory stress test on ADL-P causes UBSAN
** Tags added: lookout-canyon oem-priority originate-from-1981392
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/1996609
Title:
AX210 (8086:6020) WLAN init failed ucode -5 on
Public bug reported:
[Summary]
CPU/Memory stress test on ADL-P causes UBSAN shift-out-of-bounds in powercap.
[Steps to reproduce]
Run CPU or memory stress test
[Expected result]
No complaints in the kernel message
[Actual result]
Get UBSAN complaints in the kernel message
kernel: UBSAN:
Public bug reported:
[Summary]
AX210 (8086:6020) WLAN init failed ucode -5 on 5.15 Intel IoTG kernel.
[Steps to reproduce]
install 5.15 Intel IoTG kernel.
[Expected result]
WLAN works with no problem.
[Actual result]
Can't detect WLAN.
[Failure rate]
100%
The ucode version 66 would not be
This bug was fixed in the package linux-gcp - 5.15.0-1022.29
---
linux-gcp (5.15.0-1022.29) jammy; urgency=medium
* jammy/linux-gcp: 5.15.0-1022.29 -proposed tracker (LP: #1991987)
* Jammy update: v5.15.61 upstream stable release (LP: #1990162)
- [Config] updateconfigs for
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux-meta-hwe-5.15 -
5.15.0.53.59~20.04.21
---
linux-meta-hwe-5.15 (5.15.0.53.59~20.04.21) focal; urgency=medium
* Bump ABI 5.15.0-53.59~20.04
* build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI (LP: #1969434)
- [Packaging] hwe-5.15:
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-132.148
---
linux (5.4.0-132.148) focal; urgency=medium
* CVE-2022-42719
- mac80211: mlme: find auth challenge directly
- wifi: mac80211: don't parse mbssid in assoc response
- wifi: mac80211: fix MBSSID parsing
This bug was fixed in the package linux-azure - 5.15.0-1023.29
---
linux-azure (5.15.0-1023.29) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1023.29 -proposed tracker (LP: #1991983)
* Jammy update: v5.15.61 upstream stable release (LP: #1990162)
- [Config] azure:
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-132.148
---
linux (5.4.0-132.148) focal; urgency=medium
* CVE-2022-42719
- mac80211: mlme: find auth challenge directly
- wifi: mac80211: don't parse mbssid in assoc response
- wifi: mac80211: fix MBSSID parsing
This bug was fixed in the package linux - 5.4.0-132.148
---
linux (5.4.0-132.148) focal; urgency=medium
* CVE-2022-42719
- mac80211: mlme: find auth challenge directly
- wifi: mac80211: don't parse mbssid in assoc response
- wifi: mac80211: fix MBSSID parsing
This bug was fixed in the package linux-bluefield - 5.4.0-1050.56
---
linux-bluefield (5.4.0-1050.56) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1050.56 -proposed tracker (LP:
#1992038)
* i2c-mlxbf.c: Sync up driver with upstreaming (LP: #1991551)
- Revert "UBUNTU:
This bug was fixed in the package linux - 4.15.0-197.208
---
linux (4.15.0-197.208) bionic; urgency=medium
* bionic/linux: 4.15.0-197.208 -proposed tracker (LP: #1994998)
* Memory leak while using NFQUEUE to delegate the decision on TCP packets to
userspace processes (LP:
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.15.0-53.59
---
linux (5.15.0-53.59) jammy; urgency=medium
* Fix blank screen on Thinkpad ADL 4K+ panel (LP: #1980621)
- drm/i915: Implement WaEdpLinkRateDataReload
* Kernel regresses openjdk on riscv64 (LP: #1992484)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-132.148
---
linux (5.4.0-132.148) focal; urgency=medium
* CVE-2022-42719
- mac80211: mlme: find auth challenge directly
- wifi: mac80211: don't parse mbssid in assoc response
- wifi: mac80211: fix MBSSID parsing
This bug was fixed in the package linux - 5.4.0-132.148
---
linux (5.4.0-132.148) focal; urgency=medium
* CVE-2022-42719
- mac80211: mlme: find auth challenge directly
- wifi: mac80211: don't parse mbssid in assoc response
- wifi: mac80211: fix MBSSID parsing
This bug was fixed in the package linux-azure - 5.4.0-1095.101
---
linux-azure (5.4.0-1095.101) focal; urgency=medium
* focal/linux-azure: 5.4.0-1095.101 -proposed tracker (LP: #1992037)
* ubuntu_bpf failed to build on F-azure-5.4 / B-azure-5.4 ( error:
This bug was fixed in the package linux - 5.4.0-132.148
---
linux (5.4.0-132.148) focal; urgency=medium
* CVE-2022-42719
- mac80211: mlme: find auth challenge directly
- wifi: mac80211: don't parse mbssid in assoc response
- wifi: mac80211: fix MBSSID parsing
This bug was fixed in the package virtualbox -
6.1.38-dfsg-3~ubuntu1.20.04.1
---
virtualbox (6.1.38-dfsg-3~ubuntu1.20.04.1) focal; urgency=medium
* SRU the latest package for Ubuntu focal (LP: #1988473)
* Revert drop of *guest-dkms packages for focal only.
Such packages are
This bug was fixed in the package linux - 4.15.0-197.208
---
linux (4.15.0-197.208) bionic; urgency=medium
* bionic/linux: 4.15.0-197.208 -proposed tracker (LP: #1994998)
* Memory leak while using NFQUEUE to delegate the decision on TCP packets to
userspace processes (LP:
This bug was fixed in the package linux - 4.15.0-197.208
---
linux (4.15.0-197.208) bionic; urgency=medium
* bionic/linux: 4.15.0-197.208 -proposed tracker (LP: #1994998)
* Memory leak while using NFQUEUE to delegate the decision on TCP packets to
userspace processes (LP:
This bug was fixed in the package linux - 4.15.0-197.208
---
linux (4.15.0-197.208) bionic; urgency=medium
* bionic/linux: 4.15.0-197.208 -proposed tracker (LP: #1994998)
* Memory leak while using NFQUEUE to delegate the decision on TCP packets to
userspace processes (LP:
This bug was fixed in the package linux - 4.15.0-197.208
---
linux (4.15.0-197.208) bionic; urgency=medium
* bionic/linux: 4.15.0-197.208 -proposed tracker (LP: #1994998)
* Memory leak while using NFQUEUE to delegate the decision on TCP packets to
userspace processes (LP:
This bug was fixed in the package linux - 4.15.0-197.208
---
linux (4.15.0-197.208) bionic; urgency=medium
* bionic/linux: 4.15.0-197.208 -proposed tracker (LP: #1994998)
* Memory leak while using NFQUEUE to delegate the decision on TCP packets to
userspace processes (LP:
This bug was fixed in the package fabric-manager-470 -
470.141.10-0ubuntu0.18.04.1
---
fabric-manager-470 (470.141.10-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1993665).
-- Alberto Milone Mon, 26 Sep 2022
14:35:57 +
--
You received this bug
This bug was fixed in the package libnvidia-nscq-470 -
470.141.10-0ubuntu0.18.04.1
---
libnvidia-nscq-470 (470.141.10-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1993665).
-- Alberto Milone Mon, 26 Sep 2022
14:43:06 +
** Changed in:
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.141.10-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-470-server (470.141.10-0ubuntu0.18.04.1) bionic;
urgency=medium
* New upstream release (LP: #1993665).
* debian/rules:
- Fix regex in the modalias
This bug was fixed in the package fabric-manager-470 -
470.141.10-0ubuntu0.20.04.1
---
fabric-manager-470 (470.141.10-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1993665).
-- Alberto Milone Mon, 26 Sep 2022
14:25:52 +
** Changed in:
This bug was fixed in the package libnvidia-nscq-470 -
470.141.10-0ubuntu0.20.04.1
---
libnvidia-nscq-470 (470.141.10-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1993665).
-- Alberto Milone Mon, 26 Sep 2022
14:42:18 +
** Changed in:
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.141.10-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-470-server (470.141.10-0ubuntu0.20.04.2) focal;
urgency=medium
* New upstream release (LP: #1993665).
* debian/rules:
- Fix regex in the modalias
This bug was fixed in the package fabric-manager-470 -
470.141.10-0ubuntu0.22.04.1
---
fabric-manager-470 (470.141.10-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #1993665).
-- Alberto Milone Mon, 26 Sep 2022
12:32:09 +
** Changed in:
This bug was fixed in the package libnvidia-nscq-470 -
470.141.10-0ubuntu0.22.04.1
---
libnvidia-nscq-470 (470.141.10-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #1993665).
-- Alberto Milone Mon, 26 Sep 2022
14:41:39 +
** Changed in:
This bug was fixed in the package nvidia-graphics-drivers-470-server -
470.141.10-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-470-server (470.141.10-0ubuntu0.22.04.1) jammy;
urgency=medium
* New upstream release (LP: #1993665).
* debian/rules:
- Fix regex in the modalias
** Changed in: linux (Ubuntu Kinetic)
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/1996540
Title:
Kinetic update: upstream stable patchset
** Description changed:
[Feature Description]
This task is to identify what new device IDs are required for RPL-S.
Placeholder for RPL-S IDs that should be published.
USB device/xDCI 0x7a61 038438a25c45 v5.17-rc6
SMBus 0x7a23 9c02d4011e92 v5.18-rc1
I²C 0x7a4c 0x7a4d 0x7a4e
SRU: https://lists.ubuntu.com/archives/kernel-
team/2022-November/134769.html (oem-6.0)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ Depending on module load order there is a possibility that the AMT mode
+ selected initially by PMF will be incorrect if thinkpad_acpi has
94 matches
Mail list logo
