Kernel 6.0 seems to have fixed it for me:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v6.0/amd64/
If that works for you then it should also avoid bug 1985869 on Intel
graphics.
** Summary changed:
- HDMI over USB-C unstable since kernel 5.19 on Intel 12th Gen.
+ HDMI/DisplayPort over USB-C un
** Also affects: linux-gcp (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1953575
Title:
Update gvnic driver code
Status i
[Expired for linux-raspi (Ubuntu) because there has been no activity for
60 days.]
** Changed in: linux-raspi (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bug
** Tags added: originate-from-1989404
--
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/1989578
Title:
Add HDMI codec ID for Intel Raptor Lake
Status in HWE Next:
New
Status in
I looked around but I can't seem to find how to add the kernel. could
you tell me the command(s) or docs to try it out. thanks
On 2022-10-06 02:09, Kai-Heng Feng wrote:
> Please give this kernel a try:
> https://people.canonical.com/~khfeng/lp1970074/
>
> ** Changed in: linux (Ubuntu)
> S
** Tags added: originate-from-1990599
--
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/1991365
Title:
Fix Turbostat is not working for fam: 6 model: 191: stepping: 2 CPU
Status i
https://lkml.org/lkml/2022/10/10/1235
--
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/1970074
Title:
UBSAN: array-index-out-of-bounds in
/build/linux-9H675w/linux-5.15.0/drivers/ata/lib
Public bug reported:
unable to save my Nvidia multi monitor display configuration file
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-modules-nvidia-515-5.15.0-50-generic 5.15.0-50.56
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
Please test the kernel, which adds the affected GFX to IOMMU quirk list:
https://people.canonical.com/~khfeng/gfx-no-dmar/
--
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/1965882
Title:
[
Please test the kernel, which adds the affected GFX to IOMMU quirk list:
https://people.canonical.com/~khfeng/gfx-no-dmar/
--
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/1971146
Title:
[
** Tags added: oem-priority originate-from-1991204 somerville
--
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/1990700
Title:
Fibocom WWAN FM350-GL suspend error (notebook not suspend)
S
** Tags added: fixed-in-5.19.8 fixed-upstream
--
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/1991704
Title:
Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
Status
Public bug reported:
Automatic update failed.
package linux-intel-iotg-5.15-tools-common 5.15.0-1010.14~20.04.1
[modified: usr/share/bash-completion/completions/bpftool
usr/share/man/man1/cpupower-idle-info.1.gz usr/share/man/man1/cpupower-
monitor.1.gz usr/share/man/man1/cpupower.1.gz usr/share/
In case anyone is curious conversation is on-going on the kernel-team mailing
list
https://lists.ubuntu.com/archives/kernel-team/2022-October/133764.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
@juliank please test initrd-less boot; for example lxc launch --vm which
uses linux-kvm flavour booted without initrd.
There are differences of the mount options as applied by initramfs-
tools; systemd; and kernel itself.
--
You received this bug notification because you are a member of Kernel
P
@juliank, is this an aws system? If not there's a good chance that you
are using an initramfs to mount the filesystems. That's definited in
either /etc/init.d/udev or directly out of the init that lives in the
initramfs.
--
You received this bug notification because you are a member of Kernel
P
*** This bug is a duplicate of bug 1991704 ***
https://bugs.launchpad.net/bugs/1991704
I tried the suggested workaround of purging nvidia packages and running
ubuntu-drivers install. What I observed is that the nvidia-driver-510
packages were removed, and ubuntu-drivers subsequently installed
One of our ZFS storage servers crashed several times in the past. I was
running out of memory and ended with a kernel panic. The server did not
have a load on these occasions, as it happened on Sundays. ZFS runs its
scrubs on Sunday. (on our servers)
The pool size: 411TB
Release: Ubuntu 22.04.1 L
** Changed in: linux-riscv (Ubuntu)
Assignee: (unassigned) => Emil Renner Berthing (esmil)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1991790
Title:
Disable sv57 as the us
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/1992365
Title:
unplugging the headphones jack
I have tried `sudo apt install linux-oem-22.04a` to install linux-
image-5.17.0-1018-oem and the same problem occurs: `top` lists two, not
one, kworker processes running hot continuously.
And with linux-image-5.10.0-50-generic (released today for Ubuntu
22.04a), same problem.
--
You received thi
Public bug reported:
The Framework laptop, with 29% battery and nothing abnormal, set itself
to sleep when I pulled the audio jack to unplug my headphones.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-48-generic 5.15.0-48.54
ProcVersionSignature: Ubuntu 5.15.0-48.54-ge
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/1992362
Title:
USB stops responding on XPS932
5.4 was a long time ago, so I guess there's no point keeping this open
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1919
Public bug reported:
An intermittent problem, but to reproduce:
* unplug a USB device
* plug it back in
* notice it hasn't been detected
After this point, no amount of plugging or unplugging seems to change
anything: nothing appears in `dmesg`, `lsusb` shows only internal USB
hardware, and vid
Could you test this kernel - 5.19.0-19.19+i915fix - and report if it
fixes your issue?
https://kernel.ubuntu.com/~arighi/lp-1991703/
--
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/1990851
*** This bug is a duplicate of bug 1991951 ***
https://bugs.launchpad.net/bugs/1991951
Hi,
This bug a duplicate of bug 1991951, a fix is already applied and is
scheduled to be released with the next 5.19 kernel update.
** This bug has been marked a duplicate of bug 1991951
RCU stalls
--
** Changed in: linux (Ubuntu)
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/1991951
Title:
RCU stalls
Status in linux package in Ubuntu:
F
** Changed in: grub2-signed (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1991676
Title:
Package grub-efi-arm64-signed 1.173.2~18.04.1+2.0
*** This bug is a duplicate of bug 1991704 ***
https://bugs.launchpad.net/bugs/1991704
** This bug has been marked a duplicate of bug 1991704
Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
--
You received this bug notification because you are a member of Kernel
Pac
5.19-0-19.19+i915fix works for me.
** Attachment added: "kern.log-5.19-0-19.19+i915fix"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+attachment/5622740/+files/kern.log-5.19-0-19.19+i915fix
--
You received this bug notification because you are a member of Kernel
Packages, wh
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2004
--
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/1987287
Title:
[UBUNTU 20.04] mlx5 driver crashes on acces
sudo apt-get --purge remove '*nvidia*'
sudo ubuntu-drivers install
solved the problem for me. I am in KDE running in 5.19.0-19-generic with
Nvidia 515 drivers.
Thanks a lot.
Best regards
Heinrich
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Could you test this kernel - 5.19.0-19.19+i915fix - and report if it
fixes your issue?
https://kernel.ubuntu.com/~arighi/lp-1991703/
--
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/1991704
Hi Heinrich, I can see the following in your dmesg log:
NVRM: API mismatch: the client has the version 515.65.01, but
NVRM: this kernel module has the version 510.85.02
Can you follow these steps, please, so that we can rule out this being the main
problem?
Remove any nvidia package left on yo
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/1987249
Title:
Asus ROG Zephyrus GX701L sound
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1987249
Title:
Asus ROG Zephyrus GX701L sound problem
Status in linux packag
Public bug reported:
Every time zfs scrub executes exhaust memory hanging the server after
several hours (This is almos 600T zpool). Issue as describe in:
https://github.com/openzfs/zfs/issues/13546
-
Description:Ubuntu 22.04.1 LTS
Release:22.04
-
zfsutils-linux:
Installed: 2.1.4-0
@Alex tried with hwe kernel but issue still persists.
tried installing oem kernel, getting below error
sudo apt install linux-oem-20.04b
[sudo] password for rohit:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package linux-o
So, it looks like there are multiple issues here. The NULL pointer
dereference bug that I see in comment #25 seems to be fixed by
458ec0c8f359 ("drm/i915: fix null pointer dereference"), but this can
happen only when i915 is used.
For the other problem(s) do you happen to have a kernel oops / trac
Re-titling bug report to avoid printing unprintable characters in the
kernel upload changelog.
** Description changed:
+ earlyconsole prints on 5.19.0-1002-generic
+
[ Impact ]
* When adding earlycon to the kernel command line on the
SiFive Unmatched board t
Hello Andrea,
As expected an i915 fix is irrelevant for a system without an i915 GPU.
The problem persists with your kernel.
Best regards
Heinrich
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.laun
** Description changed:
[ Impact ]
* Linux 5.18 merged support for 5-level page tables (sv57), and it
does it such that 5-level page tables are used whenever the
system supports it.
* So far only Qemu support sv57, but it breaks Go since Go uses
too many of the upper bits o
** Description changed:
[ Impact ]
- sv57 breaks Go since Go uses the upper bits of a pointer to store data,
- and it is not ready for sv57 yet. It probably breaks other type of
- software using this "pointer tagging" technic. The following patch fixes
- this: at the moment, there is no way t
** Description changed:
[ Impact ]
- * When adding earlycon to the kernel command line on the
-SiFive Unmatched board the serial console will print garbage
-halfway through booting until entering userspace and other
-other drivers are loaded.
+ * When adding earlycon to the kern
Looking at the commits between 5.19.7 and 5.19.8 this
https://git.launchpad.net/~ubuntu-kernel-
test/ubuntu/+source/linux/+git/mainline-
crack/commit/?h=cod/mainline/v5.19.8&id=c2798203315f4729bab0b917bf4c17a159abf9f8
looks suspiciously like the fix for this issue.
--
You received this bug notifi
** Description changed:
+ [ Impact ]
+
+ * When adding earlycon to the kernel command line on the
+SiFive Unmatched board the serial console will print garbage
+halfway through booting until entering userspace and other
+other drivers are loaded.
+
+ * The problem is the UART drive
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/a
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/a
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/a
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/a
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/a
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/a
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1019.20
---
linux-oem-5.17 (5.17.0-1019.20) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1019.20 -proposed tracker (LP:
#1989787)
* Fix resume on AMD platforms when TBT monitor is plugged (LP: #1990920)
- drm/a
This bug was fixed in the package linux-raspi - 5.15.0-1016.18
---
linux-raspi (5.15.0-1016.18) jammy; urgency=medium
* jammy/linux-raspi: 5.15.0-1016.18 -proposed tracker (LP: #1989776)
* VM fails to boot in ScalingStack (LP: #1990995)
- [Packaging] raspi: Include virtio dri
On my kinetic system, /dev has nosuid, but no noexec.
** Tags added: foundations-triage-discuss
--
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/1991975
Title:
dev file system is mounted
** Attachment added: "kern.log-5.19.7"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+attachment/5622659/+files/kern.log-5.19.7
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
** Attachment added: "kern.log-5.19.6"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991704/+attachment/5622658/+files/kern.log-5.19.6
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Went through all upstream 5.19.x available at
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
5.19- OK
5.19.1 - OK
5.19.2 - OK
5.19.3 - OK
5.19.4 - no amd64 build available
5.19.5 - OK
5.19.6 - NG - same problem as reported
5.19.7 - NG - same problem as reported
5.19.8 - OK
5.1
is this an issue on 6.0?
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: In Progress => Incomplete
--
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/1989647
Title:
Fix
is this an issue on 6.0?
** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
** Changed in: linux (Ubuntu Jammy)
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.
https://bugs.launchpad.net/bugs
** Also affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.0 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.0 (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-oem-6.0 (Ubuntu Hirsute)
Status: New => In
Is there anything left to do here?
** Changed in: klibc (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: klibc (Ubuntu Cosmic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1984103
Title:
[UBUNTU 22.04] s390/qeth: cache link_info for e
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1987287
Title:
[UBUNTU 20.04] mlx5 driver crashes on accessing
So what about the missing ones then? Are those already in 6.0?
** Also affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.0 (Ubuntu Kinetic)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
This dist upgrade is a massive clusterfuck.
I disabled turbo and iommu. No change at all in performance.
I regret the upgrade. The old 20.04 worked nicely.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
Test kernel (5.19.0-19.19+i915fix) available here:
https://kernel.ubuntu.com/~arighi/lp-1991703/
It would be great if someone affected by this problem could test this
out. Thanks in advance!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Thanks Andrea for looking into the issue.
Would the code changed in 458ec0c8f359 ("drm/i915: fix null pointer
dereference") ever be executed on an AMD Ryzen processor with an Nvidia
card? Doesn't the driver framework detect that there is no i915 GPU?
--
You received this bug notification because
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux-bluefield - 5.4.0-1047.52
---
linux-bluefield (5.4.0-1047.52) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1047.52 -proposed tracker (LP:
#1989866)
* Focal update: v5.4.208 upstream stable release (LP: #1988225)
- [Config] bluef
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux-bluefield - 5.4.0-1047.52
---
linux-bluefield (5.4.0-1047.52) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1047.52 -proposed tracker (LP:
#1989866)
* Focal update: v5.4.208 upstream stable release (LP: #1988225)
- [Config] bluef
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux - 5.15.0-50.56
---
linux (5.15.0-50.56) jammy; urgency=medium
* jammy/linux: 5.15.0-50.56 -proposed tracker (LP: #1990148)
* CVE-2022-3176
- io_uring: refactor poll update
- io_uring: move common poll bits
- io_uring: kill poll
This bug was fixed in the package linux-azure - 5.15.0-1021.26
---
linux-azure (5.15.0-1021.26) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1021.26 -proposed tracker (LP: #1989754)
* Packaging resync (LP: #1786013)
- [Packaging] update variants
* Azure: Enable vPCI m
This bug was fixed in the package linux - 5.4.0-128.144
---
linux (5.4.0-128.144) focal; urgency=medium
* focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152)
* CVE-2022-3176
- io_uring: disable polling pollfree files
* ip/nexthop: fix default address selection for
This bug was fixed in the package linux - 5.4.0-128.144
---
linux (5.4.0-128.144) focal; urgency=medium
* focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152)
* CVE-2022-3176
- io_uring: disable polling pollfree files
* ip/nexthop: fix default address selection for
This bug was fixed in the package linux - 5.4.0-128.144
---
linux (5.4.0-128.144) focal; urgency=medium
* focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152)
* CVE-2022-3176
- io_uring: disable polling pollfree files
* ip/nexthop: fix default address selection for
This bug was fixed in the package linux - 5.4.0-128.144
---
linux (5.4.0-128.144) focal; urgency=medium
* focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152)
* CVE-2022-3176
- io_uring: disable polling pollfree files
* ip/nexthop: fix default address selection for
This bug was fixed in the package linux - 5.4.0-128.144
---
linux (5.4.0-128.144) focal; urgency=medium
* focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152)
* CVE-2022-3176
- io_uring: disable polling pollfree files
* ip/nexthop: fix default address selection for
This bug was fixed in the package linux - 5.4.0-128.144
---
linux (5.4.0-128.144) focal; urgency=medium
* focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152)
* CVE-2022-3176
- io_uring: disable polling pollfree files
* ip/nexthop: fix default address selection for
This bug was fixed in the package linux - 5.4.0-128.144
---
linux (5.4.0-128.144) focal; urgency=medium
* focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152)
* CVE-2022-3176
- io_uring: disable polling pollfree files
* ip/nexthop: fix default address selection for
This bug was fixed in the package linux - 5.4.0-128.144
---
linux (5.4.0-128.144) focal; urgency=medium
* focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152)
* CVE-2022-3176
- io_uring: disable polling pollfree files
* ip/nexthop: fix default address selection for
This bug was fixed in the package linux - 5.4.0-128.144
---
linux (5.4.0-128.144) focal; urgency=medium
* focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152)
* CVE-2022-3176
- io_uring: disable polling pollfree files
* ip/nexthop: fix default address selection for
This bug was fixed in the package linux - 4.15.0-194.205
---
linux (4.15.0-194.205) bionic; urgency=medium
* bionic/linux: 4.15.0-194.205 -proposed tracker (LP: #1989935)
* Bionic update: upstream stable patchset 2022-09-14 (LP: #1989625)
- random: schedule mix_interrupt_rand
This bug was fixed in the package linux - 4.15.0-194.205
---
linux (4.15.0-194.205) bionic; urgency=medium
* bionic/linux: 4.15.0-194.205 -proposed tracker (LP: #1989935)
* Bionic update: upstream stable patchset 2022-09-14 (LP: #1989625)
- random: schedule mix_interrupt_rand
This bug was fixed in the package linux - 5.4.0-128.144
---
linux (5.4.0-128.144) focal; urgency=medium
* focal/linux: 5.4.0-128.144 -proposed tracker (LP: #1990152)
* CVE-2022-3176
- io_uring: disable polling pollfree files
* ip/nexthop: fix default address selection for
This bug should be fixed by 458ec0c8f359 ("drm/i915: fix null pointer
dereference"), I'll prepare a test kernel with this fix applied on top
of 5.19.0-19.19.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://b
** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-oem-6.0 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu Jammy)
Status: New => I
1 - 100 of 107 matches
Mail list logo
