** Tags removed: kinetic
** Tags added: mantic
** Tags added: fixed-in-linux-v6.9-rc1 fixed-upstream
** No longer affects: kwin (Ubuntu)
** No longer affects: mutter (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status:
*** This bug is a duplicate of bug 2003031 ***
https://bugs.launchpad.net/bugs/2003031
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2003031, so it is being marked as such. Please
You have been subscribed to a public bug:
2024-03-29T11:15:58.111046+01:00 jan-dell gnome-shell[119359]: Page flip
failed: drmModeAtomicCommit: Device or resource busy
2024-03-29T11:15:58.112153+01:00 jan-dell kernel: [72897.470882] [
cut here ]
This is because amd-pstate is in active mode but nothing is tuning EPP
most likely.
Try to upgrade to this version of power profiles daemon:
https://launchpad.net/~superm1/+archive/ubuntu/ppd
Then you can change the power setting using the Gnome or kde GUI for it
or by using powerprofilesctl.
Public bug reported:
每次开机 提示一个报错
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Public bug reported:
GDS enables a direct data path for direct memory access (DMA) transfers
between GPU memory and storage, which avoids a bounce buffer through the
CPU. This direct path increases system bandwidth and decreases the
latency and utilization load on the CPU.
This functionality has
** Changed in: linux-nvidia-tegra (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-tegra in Ubuntu.
https://bugs.launchpad.net/bugs/2055468
Title:
apply nvidia-tegra patches 2024
** Changed in: linux-nvidia-tegra (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-tegra in Ubuntu.
https://bugs.launchpad.net/bugs/2056486
Title:
apply nvidia-tegra patches 2024
** Changed in: linux-nvidia-tegra (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-tegra in Ubuntu.
https://bugs.launchpad.net/bugs/2056594
Title:
apply nvidia-tegra patches 2024
** Changed in: linux-nvidia-tegra (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-tegra in Ubuntu.
https://bugs.launchpad.net/bugs/2058550
Title:
apply nvidia-tegra patches 2024
As a temporary workaround, you can fetch an updated release version of
crun from their GitHub and save it into /usr/local/bin.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
Public bug reported:
After the update to kernel 6.5, cpufreq no longer has options to set
most governors or frequencies. The only available options are powersave
and performance, but changing between them seem to have no effect.
Consequently, the CPU temperature is always high: while with the 6.2
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.
Public bug reported:
When I ran 2024.03.04 Focal aws-5.15 through ADT testing I got a
regression on nvidia-graphics-drivers-340 that looks different than the
previous hinting. The test log had "dpkg: error: version '-' has bad
syntax: revision number is empty". I have included the output log from
Had the same issue. Somehow, after a long power-off and turning on
again, Bluetooth managed to show up and the message was gone. Using an
AX200 as well.
Currently using kernel 6.8.2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
--- Comment From jldo...@us.ibm.com 2024-03-29 11:18 EDT---
I tested to see if mkvterm was performing as expected with the kernel in
focal-proposed, and the behavior was correct. Ritu in Novalink did as well.
In addition to that, the kernel was installed on two different lpars,
and
** Also affects: snapd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
** Also affects: snapd
Importance: Undecided
Status: New
** Changed in: snapd
Status: New => Confirmed
** Summary changed:
- Kernel 6.8 -
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/2059788
Title:
package linux-modules-nvidia-535-6.5.0-25-generic 6.5.0-25.25+1
Public bug reported:
I am trying to update ubuntu to 23.10 from 21.04 but it appears I have
both versions installed at the same partation at the same time...
Found Ubuntu 21.04 (21.04) on /dev/sda2
Adding boot menu entry for UEFI Firmware Settings ...
sudo do-release-upgrade
Checking for a new
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-restricted-modules (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
I'd like to report one more instance of this bug. BUT perhaps more
importantly pass on a condition that seems to trigger these ACPI errors
at boot time (which you may or may not realize) and which might affect
your continued approach to fixing.
I use an old Dell t7400 and just recently decided to
I'd like to report one more instance of this bug. BUT perhaps more
importantly pass on a condition that seems to trigger these ACPI errors
at boot time (which you may or may not realize) and which might affect
your continued approach to fixing.
I use an old Dell t7400 and just recently decided to
Public bug reported:
may be due to low disc space due to windows 10 update on dual boot
system
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1
ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-25-generic
** Tags removed: need-duplicate-check
--
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://bugs.launchpad.net/bugs/2059778
Title:
package linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 failed to
This is affecting J-hwe-6.5 openstack s390x instances since
6.5.0-14.14~22.04.1
** Tags added: 6.5 jammy
** Tags added: sru-20240205 sru-20240304
** Summary changed:
- net:tls in ubuntu_kernel_selftest fails sm4_* testcases on s390x Kinetic
+ net:tls in ubuntu_kernel_selftest fails sm4_*
Verified fix on jammy (not focal, sorry).
--
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/2055686
Title:
Drop ABI checks from kernel build
Status in linux package in Ubuntu:
Fix
All autopkgtests for the newly accepted linux-meta-aws-5.15
(5.15.0.1057.63~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
linux-aws-5.15/unknown (amd64, arm64)
systemd/245.4-4ubuntu3.23 (arm64)
Please visit the excuses
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.15.0-1057.63) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (armhf)
Please visit the excuses page
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.15
(5.15.0-1057.63~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (armhf)
Please visit the
Changing the state to Won't fix, because of LP: #2059762.
** Changed in: linux (Ubuntu Noble)
Status: Fix Released => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
If the issue is fixed without the extra patch, I think we can ignore it,
it was probably a false positive from UBSAN.
Let's keep an eye on it and if it shows up again in the future we can do
a test with my additional patch. Thanks for update!
--
You received this bug notification because you
Public bug reported:
[Impact]
CONFIG_INTEL_TDX_HOST depends on !KEXEC_CORE in the latest 6.8 kernel.
This was introduced by:
cb8eb06d50fc ("x86/virt/tdx: Disable TDX host support when kexec is
enabled")
We cannot regress kexec, therefore we need to disable
CONFIG_INTEL_TDX_HOST in the generic
Thank you! My issue has been resolved
** 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 Ubuntu.
https://bugs.launchpad.net/bugs/2059106
Title:
I can't install
> I'll also report back once I am able to test the new kernel.
I had a try and I was able to install it today on Noble by pulling the
deb packages for linux-image-unsigned-6.8.0-20-generic, linux-
modules-6.8.0-20-generic, linux-modules-extra-6.8.0-20-generic from
Launchpad manually.
--
You
> this system has a single DIMM which was provided by framework:
DDR5-5600 - 32GB (1 x 32GB)
My system is 8GB, single stick, same speed 5600 MT/s, same company
(A-DATA).
> Restarting firefox temporarily resolves the issue. This behavior
started to happen after I switched to X11.
You're the
I found a fix
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2059744
--
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/2000791
Title:
When my laptop wakes up from sleep, it
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2059744
--
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/1975444
Title:
mt7921e wifi fails to resume after suspend
Status in
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2059744
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/2059744
I found a fix, see here
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: hwe-next
Status: In Progress => Fix Released
--
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/bugs/2047518
Title:
Fix BCM57416 lost after resume
Status in HWE
** Changed in: hwe-next
Status: In Progress => Fix Released
--
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/bugs/2047389
Title:
Fix AMDGPU crash on 6.5 kernel
Status in HWE
** Changed in: hwe-next
Status: In Progress => Fix Released
--
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/bugs/2043786
Title:
RTL8111EPP: Fix the network lost after resume
Status changed to 'Confirmed' because the bug affects multiple users.
** 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-meta in Ubuntu.
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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,
81 matches
Mail list logo
