Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs
It also concerns « regular » Ubuntu 24.04
The reboot or shutdown hangs on for minutes ( ~5 min ) on ( maybe )
unmounting some snap :
Job run-snapd-ns-snapd\x2ddesktop\x2dintegration.mnt.mount/stop running
(4min / 4min 33s)
I can also see this kind of warnings :
evict_inodes inode ff721d
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1057.63~20.04.1 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-focal-linux-
aws-5.15' to 'verification-done-focal-lin
Last observed on Lubuntu Noble Numbat 24.04 Daily Build noble-desktop-
amd64.iso 2024-03-28 both in the Live USB boot and installed to SSD
(eMMC).
For some reason this build wont let me generated ubuntu-bug files as it
reports
*** Collecting problem information
The collected information can be s
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
All autopkgtests for the newly accepted linux-meta-azure-6.5
(6.5.0.1018.19~22.04.2) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-azure-6.5/unknown (arm64)
Please visit the excuses page listed below and investigate the fa
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
This bug is awaiting verification that the linux-aws-
fips/5.15.0-1057.63+fips1 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-aws-fips' to
'verification-done-jammy-linux-
Public bug reported:
[Overview]
I have been testing installations of a number of Lubuntu and Xubuntu Noble
Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more
latterly focused on Lubuntu.
It would appear that since introduction of Kernel 6.8 into the daily
builds, the
** Changed in: linux (Ubuntu Focal)
Status: New => Invalid
--
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/2045384
Title:
AppArmor patch for mq-posix interface is missing in ja
1. Yes. The backport was for 5.15 jammy kernels including HWE
derivatives. The user space SRU was done in bug
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1994146
which included Focal. The intent being Focal will only support mqueue if
it is using and HWE kernel.
2. Yes that makes s
This issue is still present upstream, so I reported it to the original
committer of the patch.
--
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/2058557
Title:
Kernel panic during checkbox
Anyone looking into this? I get this a few times a week especially with
multiple chromium based applications open.
--
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/2057155
Title:
amdgpu dr
Question -- this has landed in various jammy-5.15 kernels. This rolled
downstream to the focal HWE kernels (specifically the cloud kernels)
1. was this intentional?
2. if so, could we add an affects for focal as well? it'll help us with
tracking downstream dependency changes, specifically in live
I have isolated the cause of this bug to this commit:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble/commit/?h=Ubuntu-6.8.0-20.20&id=71eb6b6b0ba93b1467bccff57b5de746b09113d2
All versions that I tested before this commit during my bisect passed
the aiol test at least 15 t
*** This bug is a duplicate of bug 2049927 ***
https://bugs.launchpad.net/bugs/2049927
** This bug has been marked a duplicate of bug 2049927
since Linux kernel 6.5.0-14 external monitors are no longer detected
--
You received this bug notification because you are a member of Kernel
Packa
After setting UMA_Game_Optimized, I can confirm that (after 30 minutes
of usage), the system appears far more stable. Since X11 appeared stable
I also switched back to Wayland which was previously unusable and this
also appears to be working.
I'll also report back once I am able to test the new ke
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-6.5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bug
https://bugzilla.kernel.org/show_bug.cgi?id=218654
** Bug watch added: Linux Kernel Bug Tracker #218654
https://bugzilla.kernel.org/show_bug.cgi?id=218654
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Also affects: linux-hwe-6.5 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2047154
Title:
[amdgpu][drm] *ERROR* flip_done
Patch https://patchwork.kernel.org/project/xen-
devel/patch/171154167446.2671062.9127105384591237363.stgit@firesoul/ is
fixing the issue.
--
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/2056
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
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://bug
** Changed in: linux (Ubuntu Trusty)
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/2059143
Title:
Remove getabis scripts
Status in linux pac
*** This bug is a duplicate of bug 2046504 ***
https://bugs.launchpad.net/bugs/2046504
** This bug has been marked a duplicate of bug 2046504
AMD GPU display is blank when set lower resolution than native mode on eDP
--
You received this bug notification because you are a member of Kernel
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Xenial)
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://bug
--- Comment From kowshik.j...@in.ibm.com 2024-03-28 11:43 EDT---
(In reply to comment #13)
Hello Frank,
I upgraded the system to 6.8.0-20-generic kernel and the issue is not
seen even after multiple reboots.
Also. I took the source available here:
http://launchpadlibrarian.net/720006283/l
> If you can add your details for your "specific" FW13 AMD to the upstream bug
> maybe others who are affected can help with building the pattern.
> I mean the memory vendor, speed of memory, amount, channel configuration.
this system has a single DIMM which was provided by framework: DDR5-5600
-
Public bug reported:
The `perf` command-line tool expects a tips.txt file at
/usr/share/doc/perf-tip/tips.txt, from which it displays random tips in
`perf report` mode. If this file is not present (it is not on Ubuntu
22.04 LTS), `perf report` complains, both in interactive and in non-
interactive
** Tags removed: verification-needed-mantic-linux-azure
** Tags added: verification-done-mantic-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2057936
Title:
Azure: hv:
This has become an intermittent issue in the past few months. I am
currently on the latest 6.5 kernel and running Wayland.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2047154
Ti
Public bug reported:
The problem concerns earbuds 0B:20:24:A3:E7:56 T60 that worked perfectly
under completely patched Ubuntu 22.04 on my old machine but now refuse
to be setup on a new box running completely patched Ubuntu 22.04 . Other
old bluetooth gadgets attached without issue.
The end resul
I've build-tested on all architectures in this PPA:
https://launchpad.net/~dannf/+archive/ubuntu/mthp/+packages
I manually tested on a few systems, timing a full kernel build w/ the
Ubuntu config in a tmpfs (both to stress the system, and look for
performance differences).
- ppc64el / Power9 -
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Mantic)
Importance: High => Medium
** Changed in: linux (Ubuntu Jammy)
Importance: High => Medium
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
-
** Changed in: linux (Ubuntu Jammy)
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/2032164
Title:
A general-proteciton exception during guest
** Changed in: linux (Ubuntu Jammy)
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/2058485
Title:
[ICX] [SPR] [ipc/msg] performance: Mitigate
** 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/2038583
Title:
Turning COMPAT_32BIT_TIME off on s390x
Status
*** This bug is a duplicate of bug 2038583 ***
https://bugs.launchpad.net/bugs/2038583
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you ar
** Changed in: linux (Ubuntu)
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/1970069
Title:
Annoying boot messages interfering with splash sc
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
Hi Kowshik,
sorry, just noticed the machine data line in the log:
"IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1060.00 (NH1060_013)
hv:phyp"
Well, there is no proposed "ISO" - "-proposed" is just a special (pre-release)
area in the archive for packages, incl. kernel.
So I just thought
This bug was fixed in the package plymouth - 24.004.60-1ubuntu6
---
plymouth (24.004.60-1ubuntu6) noble; urgency=medium
* Cherry-pick upstream fixes for consistent default scale selection
that matches what Mutter chooses on the login screen (LP: #2054769)
* plymouth.hook: Stop
--- Comment From fre...@de.ibm.com 2024-03-28 03:42 EDT---
(In reply to comment #13)
> Well, I was not able to easily cherry-pick these t commits.
> I got merge conflicts due to several debug lines.
>
> After some investigations (using git blame) I found that the commits:
> 0ccac4529540 s39
I thought it was worth mentioning that sound does work via the headphone
jack on Ubuntu 23.10 and that when using the speaker, audio levels are
still detected in system settings. This makes me think all codecs etc
are working but that it's a simple toggle somewhere to get the speaker
to work rather
87 matches
Mail list logo
