** Changed in: ubuntu-fan (Ubuntu)
Assignee: (unassigned) => Akbarkhon Variskhanov (kbar)
** Changed in: ubuntu-fan (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in
This is now in progress based on LP#1978240
"Jammy update: v5.15.39 upstream stable release"
hence aligning the status.
** Changed in: ubuntu-z-systems
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: New => In Progress
--
You received this bug notification
*** This bug is a duplicate of bug 1977919 ***
https://bugs.launchpad.net/bugs/1977919
** This bug has been marked a duplicate of bug 1977919
Docker container creation causes kernel oops on linux-aws
5.13.0.1028.31~20.04.22
--
You received this bug notification because you are a member
Will have an update of the whole driver soon. Mark invalid.
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
** Tags added: oem-priority originate-from-1976234 stella
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1978252
Title:
Fix screen flickering caused by PSR on Intel TGL
Public bug reported:
TBD.
** Affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-5.17 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
**
Public bug reported:
[Impact]
Screen flickers on certain Intel TGL laptops.
[Fix]
Enable PSR2 selective fetch along with several PSR fixes.
[Test]
Screen flickers can no longer be observed on affected laptops.
[Where problems could occur]
PSR can be glitchy. Fortunately it's not system
For those who can't update, because the machine starts docker at startup
and so crashes before you can get a shell open to upgrade to 1031,
here's my method (on gcp)
stop and edit machine to detach disk
attach to another machine boot that and mount somewhere
edit /boot/grub/grub.cfg and add
Updated kernels are in flight. The updated kernel packages and versions
are:
linux-aws-5.13- 5.13.0-1029.32~20.04.1
linux-azure-5.13 - 5.13.0-1029.34~20.04.1
linux-gcp-5.13- 5.13.0-1031.37~20.04.1
linux-oracle-5.13 - 5.13.0-1034.40~20.04.1
The azure and gcp kernels are already in
Checked on a machine in my lab with that CPU (Intel Xeon Platinum 8380)
and this does not happen there...
So I'd initially blame something related to firmware, perhaps, but since
it also resolves with the 5.13 HWE, that is a little confusing.
Can you try a different CPU in this machine with 5.4
On GCP the fix hit apt. So the easiest way to fix now is simply `sudo
apt update && sudo apt upgrade`
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1977919
Title:
Docker
It happens more often when the laptop is idle.
In the logs I see a pattern of messages like:
"systemd-logind: hibernation is restricted; see man kernel_lockdown.7"
and they intensify right before the system hangs.
Secure boot is enabled, and hibernation is disabled by default. I only
use
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 1978244
and then change the status of the bug to 'Confirmed'.
If, due to the
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/1977834
Title:
not update
Status in linux
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/1977857
Title:
[amdgpu] denial of service
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Public bug reported:
[Impact]
Screen corruption can occur when s2idle resume.
[Fix]
Check that DMCUB is running and wait for auto-load.
[Test]
Verified on hardware, stress s2idle and passed.
[Where problems could occur]
Low risk, It may break s2idle on AMD GPU driver.
This commit is in 5.17.
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
For Debian and Ubuntu, I used "sudo grub-reboot 2", which forces grub
menu 2's kernel on next reboot. Once rebooted, use "dpkg-l | grep 1028"
and apt remove each package relate to kernel 1028. Apt will also update
grub for you.
Don't forget to uninstall or "break" unattended-upgrades, which is
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
@n1sni - wanted to extend my thanks as well, but on ubuntu 20.04 that
settings was not present in /etc/default/grub, so i had to uninstall
1028 and install 1025. After adding that setting, and reloading and
rebooting the change didn't take place, hence the reinstall. Going to
make an AMI, until
** Description changed:
+ SRU Justification
- 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
+
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu)
Status: Confirmed =>
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
I would like to echo earlier comments, I think that all affected kernel
packages should be pulled from the APT repositories, I also think that
all cloud images built with the bad kernel should be pulled too.
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: ubuntu-fan (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1977946
Title:
README points to non-existent URL
Status in
@n1sni - thank you for your post.
With 5.13.0-1028-aws I could only run hello-world without killing the
host.
Reverting back to 5.13.0-1025-aws from 5.13.0-1028-aws I can now run our
build containers without problems.
--
You received this bug notification because you are a member of Kernel
The fix for this bug has been awaiting testing feedback in the -proposed
repository for focal for more than 90 days. Please test this fix and
update the bug appropriately with the results. In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed
So this was painful for us. AWS hosted server running Ubuntu 20.04.4
LTS. Just for others, here are the steps we took thanks to the other
comments here:
We had to force shut down the machine and wait (aws console). Then we
got this script running, and started the machine back up:
while true; do
Public bug reported:
This panic occur only on the latest Linux kernel release.
* 5.13.0-1030-gcp is broken
* 5.13.0-1027-gcp is okay
* 5.13.0-1024-gcp is okay
Steps to reproduce:
1) Ensure kernel version is 5.13.0-1030-gcp.
2) sudo apt update
3) sudo apt install docker.io
4) sudo docker run
This is CVE-2022-1966.
** Information type changed from Private Security to Public Security
** Summary changed:
- upcoming update
+ netfilter newset stateless expression UAF
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1966
** Changed in: linux (Ubuntu)
Assignee:
Sorry for my ignorance of the software development procedure for Ubuntu,
but now that this fix has been committed, how long until it is available
via apt on the normal release channels?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Summary changed:
- upcoming update - nf oob
+ netfilter newset OOB write
--
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/1976363
Title:
netfilter newset OOB write
Status in linux
Since this is a request to port patches from upstream to Ubuntu kernels,
setting the status to 'Confirmed'.
** 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
@cz172638 - we are aware that the 5.15 Focal backport kernels have this
issue as well. However, since 5.15 is not the default -edge kernel yet,
it will have to wait until the next SRU cycle due for release 20-June,
2022.
** Changed in: linux-oracle-5.13 (Ubuntu Focal)
Importance: Undecided =>
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 1978145
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
The request is to bring vmci to TOT and back port the following patches into
Ubuntu kernels.
1. fac608138c6136126faadafa5554cc0bbabf3c44 ("VMCI: dma dg: whitespace
formatting change for vmci register defines")
2. e283a0e8b7ea83915e988ed059384af166b444c0 ("VMCI: dma dg:
** Summary changed:
- Release of nvidia-graphics-drivers 515.48.07 for Bionic, Focal, Impish,
Jammy, Kinetic
+ Release of nvidia-graphics-drivers UDA/ERD 515.48.07 for Bionic, Focal,
Impish, Jammy, Kinetic
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
Even I don't see any message that any device was found.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-44-generic 5.13.0-44.49~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-44-generic x86_64
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/1978133
Title:
System freeze followed by
i'm seeing the same on an asm1064+jbm575 sata pcie card.
it also appears to completely break one of the cards if you 2 sata pcie cards
connected too.
ie: i've recently bought and added an asm1166+jmb575 card which appears to work
on all ports. the existing asm1064 based card is now failing to
** Attachment added: "journalctl blank screen"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1978133/+attachment/5595973/+files/journalctl-blank-screen.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Bug confirmed on Oracle Cloud running Ubuntu 20.04.4 Kernel
5.13.0-1033-oracle.
Workaround with ssh by Gerard(g-kok) works. thx
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.13 in Ubuntu.
Public bug reported:
System keeps freezing in many different circumstances. I don't know how
to reproduce this.
Only happens on Ubuntu 22.04. Earlier versions were fine - tested Ubuntu
impish and Debian bullseye.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package:
The fabric-manager-510 and libnvidia-nscq-510 were tested across all
series on an A100 system. All testing passed the standard cuda testing.
The packages tested were from https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/ppa/+packages?field.name_filter=-510_filter=published_filter=
--
linux-intel-iotg-5.15:
5.15.0-1003 good
5.15.0-1008 bad
also reproducer (using podman) is smaller:
podman run --rm -it alpine:3.16 ls
which knocks down system
versus
podman run --rm -it busybox ls
which doesn't
--
You received this bug notification because you are a member of Kernel
@mruffel:
interesting, I am right now already at 5.15.0-37-generic from:
APT-Sources: http://de.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
I gave up with custom Kernels as it seemed they provide no clear
improvement better then running the ubuntu package with iommu turned of
as
I can confirm going back to 5.13.0-1027-gcp from 5.13.0-1030-gcp fixed
it for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1977919
Title:
Docker container creation causes
Taking a screenshot definitely triggers this for me, although it also
happens on other occasions.
--
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/1971428
Title:
CPU pipe A FIFO underrun
OK, I have tried stock ubuntu kernel version 5.15.0-37-generic
With /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="verbose intel_iommu=off"
firmware loads, wifi works.
[ 15.752699] iwlwifi :3d:00.0: loaded firmware version 17.3216344376.0
7260-17.ucode op_mode iwlmvm
[ 15.867847]
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include
We can confirm on: 5.13.0-1028-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1977919
Title:
Docker container creation causes kernel oops on linux-aws
@timg-tpi Yes, in https://bugs.launchpad.net/bugs/1977973 I found
5.13.0-1027-gcp to work fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1977919
Title:
Docker container
** Tags added: upstream-stable
--
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/1977508
Title:
[UBUNTU 20.04] zfcp: fix failed recovery on gone remote port, non-NPIV
FCP dev
Status in
** Tags added: tracking-upstream-stable
** Tags removed: tracking-upstream-stable
** Tags added: upstream-stable
--
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/1976533
Title:
[UBUNTU
** Tags added: upstream-stable
--
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/1977510
Title:
[UBUNTU 20.04] hypfs: fix listing z/VM guests with access control
group set
Status in
I'm glad to see that commit:
c9bfb460c3e4 c9bfb460c3e4da2462e16b0f0b200990b36b1dd2 "s390/perf: obtain
sie_block from the right address"
is tagged (upstream) for stable updates with:
Cc: sta...@vger.kernel.org
With that, this commit will automatically be picked up by the Ubuntu kernel
teams
@electricdaemon - please start a new bug report with sufficient detail
that someone can diagnose the problem. Is this a regression from
previous versions ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.13 in Ubuntu.
@electricdaemon - please start a new bug report with sufficient detail
that someone can diagnose the problem. Is this a regression from
previous versions ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.13 in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1967856/+attachment/5595908/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1967856/+attachment/5595905/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1967856/+attachment/5595906/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1967856/+attachment/5595910/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1967856/+attachment/5595907/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1967856/+attachment/5595909/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1967856/+attachment/5595911/+files/acpidump.txt
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1967856/+attachment/5595904/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1967856/+attachment/5595903/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1967856/+attachment/5595902/+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/1967856
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1967856/+attachment/5595901/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This issue has been fixed by a patch to the openvswitch datapath code in
the kernel [0].
The patched kernel would be required when used in conjunction with OVN
21.12 or newer, which translates to Focal (yoga UCA), Jammy and Kinetic.
0:
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 1967856
and then change the status of the bug to 'Confirmed'.
If, due to the
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: openvswitch (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
not installed
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-firmware 20220329.git681281e4-0ubuntu3.2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
below kernels on azure have this issue. please hold on the new images which
contain these kernel releases. thanks.
focal/linux-azure-5.13: 5.13.0-1026-azure
focal/linux-azure-5.15: 5.15.0-1008-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags added: oem-priority originate-from-1977682 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1977835
Title:
Focal update: upstream stable patchset 2022-06-07
Test kernel posted fixes crash but has another bug with unkillable stuck
defunct docker-proxy service causing more issues. Bug is not solved.
Tested on Linux AWS Lightsail instance.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
This issue was fixed by a patch to `bluetooth-next`, which was accepted
into the v5.15 kernel included with Ubuntu 22.04 LTS.
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-
next.git/commit/?id=340cd23d9dec58b1b07ecaa205a161faf50eab8a
I can confirm that, if present, the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-intel-iotg-5.15 (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.13 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-intel-iotg-5.15 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.13 in Ubuntu.
** Tags added: jellyfish-edge-staging
--
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/1842320
Title:
Out of Memory on boot with 5.2.0 kernel
Status in grub:
Unknown
Status in OEM
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Fix Released => 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/1971144
Title:
Black
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1924741
Title:
Load Broadcom firmware for Dell Bluetooth device
** Also affects: linux-intel-iotg-5.15 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1977919
Title:
Docker container
You have been subscribed to a public bug:
After I log in from the login screen, I just get a black screen. To get
a GUI, I then press "CTL+Alt+F4", to get a console login, and then do
"sudo startx". I have tried both options from the bottom right corner
for logging in.
ProblemType: Bug
Just updating to mention this problem is still present in 5.13.0-48
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe in Ubuntu.
https://bugs.launchpad.net/bugs/1973086
Title:
System won't go into suspend normally with kernel
--- Comment From boris.m...@de.ibm.com 2022-06-09 03:12 EDT---
*** Bug 198475 has been marked as a duplicate of this bug. ***
--
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/1977962
** Changed in: mutter (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 in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update [Failed to
also present in linux-image-5.15.0-1008-intel-iotg:
##
[ 1666.319425] [ cut here ]
[ 1666.319433] kernel BUG at include/linux/fs.h:3082!
[ 1666.319443] invalid opcode: [#3] SMP NOPTI
[ 1666.319449] CPU: 0 PID: 17586 Comm:
hit same problem using podman in rootless on linux-image-5.15.0-1008-intel-iotg:
##
[ 1666.319425] [ cut here ]
[ 1666.319433] kernel BUG at include/linux/fs.h:3082!
[ 1666.319443] invalid opcode: [#3]
I'm glad to see that the commit:
663d34c8df98 663d34c8df98740f1e90241e78e456d00b3c6cad "s390/hypfs: include z/VM
guests with access control group set"
got tagged for stable update:
"Cc: sta...@vger.kernel.org"
With that, such commits will automatically be picked up by the Ubuntu kernel
team's
"
I'm glad to see that the commit:
8c9db6679be4 8c9db6679be4348b8aae108e11d4be2f83976e30 "scsi: zfcp: Fix failed
recovery on gone remote port with non-NPIV FCP devices"
got tagged for stable update:
"Cc: #2.6.32+"
With that, such commits will automatically be picked up by the Ubuntu kernel
teams
I'm glad to see that both commits:
5b53a405e465 5b53a405e4658580e1faf7c217db3f55a21ba849 "s390/dasd: fix data
corruption for ESE devices"
and
71f387165737 71f3871657370dbbaf942a1c758f64e49a36c70f "s390/dasd: prevent
double format of tracks for ESE devices"
are tagged for stable updates:
"Cc:
** Description changed:
[Impact]
-
+ During suspend and resume, system would hang.
[Fix]
-
+ The impact of this regression is the same for resume that I saw on
+ thaw: the kernel hangs and nothing except SysRq rebooting can be done.
+
+ Fixes regression in commit cbe6c3a8f8f4 ("net:
95 matches
Mail list logo
