** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs-tools (Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firmware-sof (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firmware-sof (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchp
** Changed in: linux (Ubuntu Noble)
Status: New => 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/2051342
Title:
Enable lowlatency settings in the generic kernel
St
I've analysed a couple of Noble systems today and don't think initramfs-
tools needs improving (although it might not hurt). On both systems,
plymouth-start was within 1 second of simpledrm starting (same
timestamp), but the bug still occurs. The reasons are:
1. One system actually experiences the
You can test if the above suggestion will work for you by adding these
kernel parameters:
loglevel=3 fsck.mode=skip
--
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/1970069
Title:
Annoy
Maybe initramfs-tools does still need changing. plymouth-start.service
seems to run twice, and I get the feeling only the second instance is
actually succeeding in splashing on screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
You have been subscribed to a public bug:
---Problem Description (by far...@us.ibm.com) ---
Cannot use vfio-ccw dasd passthrough for KVM guests under Ubuntu 20.04/22.04
Contact Information = Eric Farman
---uname output---
Linux m34mkvmt5 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 21:05:01
Public bug reported:
---Problem Description (by far...@us.ibm.com) ---
Cannot use vfio-ccw dasd passthrough for KVM guests under Ubuntu 20.04/22.04
Contact Information = Eric Farman
---uname output---
Linux m34mkvmt5 5.4.0-135-generic #152-Ubuntu SMP Wed Nov 23 21:05:01 UTC 2022
s390x s390x
** Package changed: linux (Ubuntu) => libvirt (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: libvirt (Ubuntu)
Assignee: Skipper B
Safety is paramount in any event, especially those involving active
play. Thankfully, party inflatables are designed with safety in mind,
constructed from sturdy materials and equipped with features such as
reinforced seams and secure anchoring systems. Additionally, many rental
companies provide t
Even if FRAMEBUFFER=Y wasn't added, I think that a change to stop adding
all those other drm drivers makes a lot of sense. No use doubling the
initrd size for the LUKS case.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
an interesting amdgpu issue:
I currently have two external monitors, and only one will display the
desktop at a time - the other is completely white. The interesting thing
is that with each interrupt that the kernel receives from keyboard /
mouse, the screens will flip which
Public bug reported:
Summary:
create hfs file system, loop-back mount it, run iomix stessor with
stress-ng to exercise with a mix of file I/O operations and remove files
at end. File system is empty but a lot of blocks are used and can't seem
to be recovered.
Kernel: 6.8.0-11-generic
test case:
Possibly related? https://bugs.kde.org/show_bug.cgi?id=462214 This bug
seems to be for gnome. It looks KDE fixed kwin if I am correctly
understanding the bug.
** Bug watch added: KDE Bug Tracking System #462214
https://bugs.kde.org/show_bug.cgi?id=462214
** Changed in: kwin (Ubuntu)
Sta
Public bug reported:
Summary:
create hfs file system, loop-back mount it, run filename stressor with
stress-ng to exercise filename create/stat/unlink and we get unexpected -EEXIST
errors.
This can be worked around by adding a sync() call after the unlink() to ensure
metadata is sync'd.
Kerne
** 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 member
** 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 mem
** 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 stage2_apply_ra
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
https://help
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
https://help
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
** 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 DP
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 encou
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
* A
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
** 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 pac
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 remo
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
[ Ub
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 - 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: 5.15.0-100.
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 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 e
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 pro
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'. I
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 t
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 pro
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
'verification-done-jammy-linux-in
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
'verification-done-jammy-linux-in
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'. I
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
'verification-done-jammy-linux-in
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 t
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 pro
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 pro
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
'verification-done-jammy-linux-in
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 pro
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'. I
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 t
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'. I
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 t
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
'verification-done-jammy-linux-in
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'. I
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 pro
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 t
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
'verification-done-jammy-linux-in
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'. I
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 pro
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 t
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 incl
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. NG
** 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: chm
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
Status:
** 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
2d83fb0
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)
I
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 ex
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 ex
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 ex
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 ex
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 ex
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 ex
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 ex
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 ex
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 ex
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 ex
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 ex
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 ex
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 ex
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 ex
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 ex
** 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 up
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 no
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)
(powerpc64le-linu
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
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.
https://bugs.launchp
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
.proc.driver.nvidi
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
St
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 pack
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 nvid
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.
https://bugs.launchpad.net/bugs/20
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 Ubunt
1 - 100 of 116 matches
Mail list logo