** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Importance: Undecided => Critical
** Tags added: noble ppc64el
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Indeed this doesn't seem to have happened since 2020.
** No longer affects: mutter (Ubuntu)
** No longer affects: plasma-desktop (Ubuntu)
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You
No it's not coming back:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=1f7b328c9ab26721106fc83522f01ace42239988
Why is there a test dependency on a docs package? That seems wrong.
** Changed in: linux (Ubuntu)
Status: New => Won't Fix
--
You received
I cannot reproduce this on noble ( plasma-desktop ) I logged out,
CTRL+ALT+F? worked as expected.
** Changed in: plasma-desktop (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.29
---
linux-firmware (20220329.git681281e4-0ubuntu3.29) jammy; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.29
---
linux-firmware (20220329.git681281e4-0ubuntu3.29) jammy; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.29
---
linux-firmware (20220329.git681281e4-0ubuntu3.29) jammy; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.29
---
linux-firmware (20220329.git681281e4-0ubuntu3.29) jammy; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware
This bug was fixed in the package linux-firmware -
20220329.git681281e4-0ubuntu3.29
---
linux-firmware (20220329.git681281e4-0ubuntu3.29) jammy; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware
The verification of the Stable Release Update for linux-firmware 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
The verification of the Stable Release Update for linux-firmware 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
The verification of the Stable Release Update for linux-firmware 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
The verification of the Stable Release Update for linux-firmware 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
The verification of the Stable Release Update for linux-firmware 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
All autopkgtests for the newly accepted linux-meta (5.15.0.102.99) for jammy
have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/249.11-0ubuntu3.12 (arm64, armhf, ppc64el, s390x)
Please visit the excuses page listed below and
Public bug reported:
Mar 7 19:07:10 ripper kernel: [9.873519] UBSAN: array-index-out-of-bounds
in
/build/linux-hwe-6.5-YpKOvT/linux-hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/smu7_hwmgr.c:3676:4
Mar 7 19:07:10 ripper kernel: [9.873531] index 7 is out of range for
I am running the x.org X server Nouveau display driver now. I will
advise.
--
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/2054121
Title:
Random Freezing
Status in linux package in
You will actually get Wayland by default if the Nvidia driver is
uninstalled. So try that as well as Xorg (selectable on the login
screen).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Use x.org X server Nouveau dissplay drivers?
--
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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Status in
Get it. Thanks~
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2051199
Title:
Add MediaTek Genio mt8370 support and update mt8390 and mt8395 configs
Status in alsa-ucm-conf
Thanks. Next I would resort to drastic measures: Uninstall the Nvidia
driver completely. Then wait and see if that's eliminated the freezes.
** Package changed: ubuntu => linux (Ubuntu)
** Tags added: nvidia
** Also affects: nvidia-graphics-drivers-545 (Ubuntu)
Importance: Undecided
You have been subscribed to a public bug:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
I also have this issue the machines that have this issue have all been
upgraded from jammy. This happens both on virtual servers and bare metal
installs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
re-tested with today's image http://cdimage.ubuntu.com/ubuntu-
server/daily-live/20240307/ - same
--
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/2056491
Title:
not able to install noble
This is happening with Kernel 6.8 (currently available image noble-live-
server-ppc64el.iso `2024-03-05 09:03`). I was able to install noble on
the same systems last week, when Noble still had kernel 6.6.
I'm also able to install Jammy 22.04.4 on both mentioned LPARs - P9 and
P10.
The issue is
Public bug reported:
After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le
Power9 or Power10 :
error: out of memory.
Press any key to continue...
OF stdout device is: /vdevice/vty@3000
Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003)
** Description changed:
[Impact]
- Some improvement are made to qat which makes it
- more resilient and able to handle reset in a
- better way.
+ This set improves the error recovery flows in the QAT drivers and
+ adds a mechanism to test it through an heartbeat simulator.
- There is an
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-102.112 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-linux' to 'verification-done-jammy-linux'. If
the problem still
Public bug reported:
zfs-linux autopkgtest depends on linux-doc.
However, linux-doc binary package is removed. Is this removal intentional? And
if there a replacement package for it?
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: zfs-linux (Ubuntu)
** Description changed:
[Impact]
This update has been initiated to include a few critical bug fixes from
upstream into the upcoming 22.04.04 point kernel. Below are the upstream
commit IDs:
[Fix]
0938f9fa4208 scsi: megaraid_sas: Driver version update to 07.727.03.00-rc1
Public bug reported:
Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-tegra
and linux-nvida-tegra-igx).
** Affects: linux-nvidia-tegra (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-nvidia-tegra-igx (Ubuntu)
Importance: Undecided
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2052961
Title:
Error: OCI runtime error: crun:
Public bug reported:
SRU Justification:
[Impact]
In Ubuntu AMIs for x86 and Graviton based EC2 instances, the standard
Ubuntu AMI comes without IRQ moderation enabled for ENA, which for our
latest generation instances with networking heavy workloads is up to a
25% performance regression (i.e.
Hi Chandrakanth,
Thank you for filing is the requested fields. I have one more request,
can you also add what the regression risk will be? This will be
included under [ Where problems could occur ].
Thanks,
Michael
** Description changed:
[Impact]
This update has been initiated to
This bug is awaiting verification that the linux-raspi/5.15.0-1048.51
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-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-kvm/5.15.0-1052.57
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-linux-kvm' to 'verification-done-jammy-
linux-kvm'. If the
This bug is awaiting verification that the linux-oracle/5.15.0-1053.59
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-linux-oracle' to 'verification-done-
jammy-linux-oracle'.
This bug is awaiting verification that the linux-raspi/5.15.0-1048.51
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-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1050.56 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-linux-intel-iotg' to
This bug is awaiting verification that the linux-kvm/5.15.0-1052.57
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-linux-kvm' to 'verification-done-jammy-
linux-kvm'. If the
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1050.56 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-linux-intel-iotg' to
This bug is awaiting verification that the linux-oracle/5.15.0-1053.59
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-linux-oracle' to 'verification-done-
jammy-linux-oracle'.
This bug is awaiting verification that the linux-raspi/5.15.0-1048.51
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-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-oracle/5.15.0-1053.59
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-linux-oracle' to 'verification-done-
jammy-linux-oracle'.
This bug is awaiting verification that the linux-oracle/5.15.0-1053.59
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-linux-oracle' to 'verification-done-
jammy-linux-oracle'.
This bug is awaiting verification that the linux-raspi/5.15.0-1048.51
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-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-kvm/5.15.0-1052.57
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-linux-kvm' to 'verification-done-jammy-
linux-kvm'. If the
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1050.56 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-linux-intel-iotg' to
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1050.56 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-linux-intel-iotg' to
This bug is awaiting verification that the linux-raspi/5.15.0-1048.51
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-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-kvm/5.15.0-1052.57
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-linux-kvm' to 'verification-done-jammy-
linux-kvm'. If the
This bug is awaiting verification that the linux-kvm/5.15.0-1052.57
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-linux-kvm' to 'verification-done-jammy-
linux-kvm'. If the
This bug is awaiting verification that the linux-oracle/5.15.0-1053.59
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-linux-oracle' to 'verification-done-
jammy-linux-oracle'.
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1050.56 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-linux-intel-iotg' to
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1050.56 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-linux-intel-iotg' to
This bug is awaiting verification that the linux-kvm/5.15.0-1052.57
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-linux-kvm' to 'verification-done-jammy-
linux-kvm'. If the
This bug is awaiting verification that the linux-oracle/5.15.0-1053.59
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-linux-oracle' to 'verification-done-
jammy-linux-oracle'.
This bug is awaiting verification that the linux-raspi/5.15.0-1048.51
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-linux-raspi' to 'verification-done-jammy-
linux-raspi'. If
This bug is awaiting verification that the linux-kvm/5.15.0-1052.57
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-linux-kvm' to 'verification-done-jammy-
linux-kvm'. If the
This bug is awaiting verification that the linux/4.4.0-252.286 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-xenial-linux' to 'verification-done-xenial-linux'.
If the problem still
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug was fixed in the package linux-hwe-5.15 -
5.15.0-100.110~20.04.1
---
linux-hwe-5.15 (5.15.0-100.110~20.04.1) focal; urgency=medium
* focal/linux-hwe-5.15: 5.15.0-100.110~20.04.1 -proposed tracker
(LP: #2052087)
[ Ubuntu: 5.15.0-100.110 ]
* jammy/linux:
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug was fixed in the package linux - 5.15.0-100.110
---
linux (5.15.0-100.110) jammy; urgency=medium
* jammy/linux: 5.15.0-100.110 -proposed tracker (LP: #2052616)
* i915 regression introduced with 5.5 kernel (LP: #2044131)
- drm/i915: Skip some timing checks on BXT/GLK
This bug was fixed in the package linux-azure - 5.15.0-1058.66
---
linux-azure (5.15.0-1058.66) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1058.66 -proposed tracker (LP: #2052049)
* Azure: Enable CONFIG_TEST_LOCKUP (LP: #2052723)
- [Config] CONFIG_TEST_LOCKUP=m
[
Commit "eventfs: Do not allow NULL parent to eventfs_start_creating()" had to
be dropped.
This introduced a warning: "WARNING: CPU: 17 PID: 1 at fs/tracefs/inode.c:408
start_creating+0xe9/0x110" that can be seen during boot testing. The check
itself would not be an issue, but the commit was
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
--
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/2056354
Title:
qat: Improve error/reset handling
Status in linux
This bug was fixed in the package alsa-ucm-conf - 1.2.9-1ubuntu3.3
---
alsa-ucm-conf (1.2.9-1ubuntu3.3) mantic; urgency=medium
* Dropped changes:
- d/p/0001-Add-initial-support-for-MediaTek-mt8390-evk-and-mt83.patch
- replace it with patches accepted by upstream
* Added
This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu1.11
---
alsa-ucm-conf (1.2.6.3-1ubuntu1.11) jammy; urgency=medium
* Dropped changes:
- d/p/0001-Add-initial-support-for-MediaTek-mt8390-evk-and-mt83.patch
- replace it with patches accepted by upstream
*
The verification of the Stable Release Update for alsa-ucm-conf 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
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2056364
Title:
Add test script for
Ethan, thanks for the verification.
In the future, please include the exact version of the package that you
tested, and where it came from. I.e., the output of "apt-cache policy
" shows all that information.
There have been a few cases in the past where the verification was
mistakenly done using
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=218571.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Launchpad has imported 1 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=218570.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056227
Title:
KVM: arm64: softlockups in
** Summary changed:
- weird file system free block state after creating files and removing them
with a mix of i/o operations
+ hfs: weird file system free block state after creating files and removing
them with a mix of i/o operations
--
You received this bug notification because you are a
** Bug watch added: Linux Kernel Bug Tracker #218571
https://bugzilla.kernel.org/show_bug.cgi?id=218571
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=218571
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
1 - 100 of 116 matches
Mail list logo
