This issue is s390-specific only, and does not affect aws at all.
Hence adding tag verification-done again to potentially unblock the process.
** Tags removed: verification-needed-jammy-linux-aws-6.5
verification-needed-jammy-linux-gcp-6.5 verification-needed-mantic-linux-azure
** Tags added:
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1015.16
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-oem-6.5' to 'verification-done-
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1015.16
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-oem-6.5' to 'verification-done-
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1015.16
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-oem-6.5' to 'verification-done-
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1015.16
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-oem-6.5' to 'verification-done-
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1015.16
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-oem-6.5' to 'verification-done-
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1015.16
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-oem-6.5' to 'verification-done-
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1015.16
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-oem-6.5' to 'verification-done-
This issue is s390x only, and not related to aws at all.
Hence adding verification-done again to potentially unblock the process.
** Tags removed: verification-needed-jammy-linux-aws-6.5
verification-needed-jammy-linux-gcp-6.5 verification-needed-mantic-linux-azure
** Tags added:
I checked it in kernel 6.5.0-15-generic, the HDD heads are parked
correctly.
--
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/2053104
Title:
Kernel 6.5.0-17-generic HDD loudly parks heads
** Summary changed:
- HDD loudly parks heads in emergency mode
+ Kernel 6.5.0-17-generic HDD loudly parks heads in emergency mode
--
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/2053104
sudo lspci -vnvn > lspci-vnvn.log
** Attachment added: "lspci-vnvn"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2053104/+attachment/5746257/+files/lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
[Expired for linux-signed-hwe-6.2 (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
When power is turned off, HDD drives park their heads loudly. This does
not happen when using the 6.2.0-39-generic kernel, or when turning off
the power after booting into Windows 10.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: hdd
Public bug reported:
3rd party kernel modules for Ubuntu 20.04 break due to the recently
backported change of renaming GENHD_FL_NO_PART_SCAN to GENHD_FL_NO_PART
linux-gcp-5.15-headers-5.15.0-1049 still uses GENHD_FL_NO_PART_SCAN
which the 3rd party kernel modules use, while linux-
This bug is awaiting verification that the linux-azure/6.5.0-1015.15
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Second (external) monitor not active after screen lock
+ [nvidia] Second (external) monitor not active after screen lock
You have been subscribed to a public bug:
After switching back to Xorg, I have encountered the issue with the
second (external) monitor - after the screen is locked and I unlock it,
the second monitor either shows a blank black screen or is not even
active in Display settings. It's like the
** Tags removed: verification-needed-jammy-linux-hwe-6.5
verification-needed-mantic-linux
** Tags added: verification-done-jammy-linux-hwe-6.5
verification-done-mantic-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
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.
I just bought new drives for 2k dollars because of this.
Then I realised it was this kernel update.
Can confirm, retracts (192) and hdd's gets hard shutdowns.
(Power cycle) also increases as if the PC had power loss.
This will break many old drives!
Backing to previous kernel solves it.
--
** Changed in: linux-gcp (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/2052576
Title:
GCP TDX Support
Status in
--- Comment From cha...@us.ibm.com 2024-02-13 16:49 EDT---
(In reply to comment #14)
> I did a screening of the traces, but couldn't really find suspicious entries.
> I'm now looking for a someone else's view and opinion...
Thanks Frank! I hope you found someone else to help you. Please
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Philip Cox (philcox)
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Public bug reported:
This is a public version of https://bugs.launchpad.net/bugs/2034983
[Description]
When running UnixBench/shell1 cases, we observed high false
sharing for accessing i_mmap against i_mmap_rwsem.
The patch places the i_mmap and i_mmap_rwsem in separate cache lines to avoid
Hi All,
We have covered the driver validation on the provided kernel and haven't
found any issues. Thank you.
--
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/2045233
Title:
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 in Ubuntu.
https://bugs.launchpad.net/bugs/2052842
** Changed in: dkms (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2051414
Title:
package linux-image-unsigned-6.5.0-15-generic 6.5.0-15.15
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
This bug is awaiting verification that the linux-
aws-6.5/6.5.0-1013.13~22.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-jammy-linux-
aws-6.5' to
It may have to do with this issue also.
https://github.com/longhorn/longhorn/issues/6887
It is confirmed by several longhorn users after updating to kernel
5.15.0-94. Previous kernel works as expected.
** Bug watch added: github.com/longhorn/longhorn/issues #6887
** Description changed:
- screen goes completely white, have to reboot the system to recover
+ Screen goes completely white, have to reboot the system to recover. I've
+ manually attached the kernel log from the previous boot which contains
+ the relevant errors.
ProblemType: Bug
Public bug reported:
[Bug Description]
cpufreq governor fails to start after installing Ubuntu 22.04.3LTS w/
latest kernel
[Steps to Reproduce]
1) Booted Ubuntu 22.04.3 LTS w/ 5.15.0-94-generic
2) dmesg | grep cppc shows no driver
3) lsmod | grep cppc shows that cppc-cpufreq is not loaded
4)
** Changed in: linux-azure (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
Public bug reported:
After the last kernel upgrade, I noticed that, in the S.M.A.R.T.
monitor, parameter ID 192 "Power Off Retract Count" increased every time
I turned off the system. I also noticed the "click" of the head parking
when shutting down the computer. By restarting the computer with
Public bug reported:
screen goes completely white, have to reboot the system to recover
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.6.0-14-generic 6.6.0-14.14
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion:
I'm in the same situation as Soenke: The bug occurs on my work laptop on
22.04 HWE (6.5.0-17). The Jammy proposed repository only offers 6.5.0-18
currently, so I can't test this.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2004
--
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/2038587
Title:
Turning COMPAT_32BIT_TIME off on ppc64el
Public bug reported:
An error occurs when using the browser after rebooting after
installation.
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: nvidia-dkms-545 545.29.06-0ubuntu0.23.10.2
Uname: Linux 6.6.0-060600-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
Jammy update:
Due to lack of reproduction environment I have been performing following
regression test:
1. Setup:
nic: 2port E810-XXV
both interfaces set up in bonding
kernel: 5.15.0-100-generic
2. Test cases:
0) verified that code from the change is used during driver init
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
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/2051896
Title:
Fix spurious wakeup caused by
** Changed in: linux-oem-6.5 (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-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051334
Title:
There is sound from the
** Changed in: linux-oem-6.5 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => Fix Committed
--
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/2049838
Title:
Mute/mic LEDs no function on HP
** Changed in: linux-oem-6.5 (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-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051050
Title:
Audio balancing setting
** Changed in: linux-oem-6.5 (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-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051341
Title:
black screen when wake up
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => Fix Committed
--
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/2051846
Title:
Mute/mic LEDs no function on HP
74 matches
Mail list logo
