** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Portia Stephens
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
There is no ARM64 for intel iotg kernel.
** Tags removed: verification-needed-jammy-linux-intel-iotg
** Tags added: verification-dibe-jammy-linux-intel-iotg
** Tags removed: verification-dibe-jammy-linux-intel-iotg
** Tags added: verification-done-jammy-linux-intel-iotg
--
You received this
I ran the above test:
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-dannf-test/jammy/amd64/l/livecd-rootfs/20240123_035147_6470b@/log.gz
It does appear that systemd-udevd is trying to scan partitions at the
same time as losetup:
1599s ++ losetup --show -f -P -v
** Tags added: 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/2049637
Title:
Some SPR systems throw kernel warnings from uncore_discovery.c
Status in intel:
Confirmed
Status in
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Commit 65248a9a9ee1 (perf/x86/uncore: Add a quirk for UPI on SPR) needs
some code adaptations when backporting to kernel 5.15.
I just made an adapted patch locally. Here attached. Please try to apply
and test.
** Patch added: "0001-perf-x86-uncore-Add-a-quirk-for-UPI-on-SPR.patch"
** Summary changed:
- brightness
+ [HP EliteBook 8560w] Can't change screen brightness
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
amdgpu.mcbp=0
Does not work for me.
On Mon, Jan 22, 2024 at 7:51 PM samuelbailey <2039...@bugs.launchpad.net>
wrote:
> Not completely sure whether this is an identical issue, but at the very
> least looks very similar, I was seeing:
>
> UBSAN: array-index-out-of-bounds in
** Package changed: bluez (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049958
Title:
package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to
make
You have been subscribed to a public bug:
hi , i can't change my brightness it s blocked on max even if i us fn+f9
it show the bar of brightness changing but not the brightness in my
screen
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu
I was able to reproduce the hang problem using the script mdhang.sh
(modified for my raid device location) on 22.04 with kernel 5.15 several
times, usually within 10-15 minutes.
Using 22.04 hwe kernel 6.5 I was not able to reproduce the problem with
a 25+ hours run of the same script. Seems
All autopkgtests for the newly accepted linux-meta-lowlatency (5.15.0.94.94)
for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-lowlatency/5.15.0-94.104 (amd64, arm64)
systemd/249.11-0ubuntu3.11 (arm64)
Please visit the
** Also affects: nvidia-graphics-drivers-525 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu.
https://bugs.launchpad.net/bugs/2049635
Title:
All autopkgtests for the newly accepted linux-meta-nvidia (5.15.0.1044.44) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
wireguard/unknown (arm64)
Please visit the excuses page listed below and investigate the failures,
Not completely sure whether this is an identical issue, but at the very
least looks very similar, I was seeing:
UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-q7NZ0T/linux-
hwe-6.5-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/powerplay/hwmgr/vega10_processpptables.c:621:5
A workaround
So I encountered this recently as well. I've got some strong evidence
that at least part of the problem is the SMB *server*, specifically a
Synology NAS.
We are migrating from a TrueNAS to Synology, and I noticed the timestamp
issue after rsync'ing files from an Ubuntu 22.04 client. I simplified
Removing packages from noble:
nvidia-graphics-drivers-515-server 515.105.01-0ubuntu2 in noble
libnvidia-cfg1-510-server 515.105.01-0ubuntu2 in noble amd64
libnvidia-cfg1-510-server 515.105.01-0ubuntu2 in noble arm64
Removing packages from noble:
nvidia-graphics-drivers-460 460.91.03-0ubuntu1 in noble
libnvidia-cfg1-450 460.91.03-0ubuntu1 in noble amd64
libnvidia-cfg1-455 460.91.03-0ubuntu1 in noble amd64
libnvidia-common-450 460.91.03-0ubuntu1 in noble
Hello,
After some additional investigation it seems more to some kind of problem with
Standby mode.
I checked this discussion and tried the AMD S2IDLE analysis script to debug
ACPI standby.
https://discussion.fedoraproject.org/t/please-improve-the-s0ix-experience-under-linux/79113/2
But no new
All autopkgtests for the newly accepted linux-restricted-modules-nvidia
(5.15.0-1044.44) 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
Same for 515-server:
$ reverse-depends src:nvidia-graphics-drivers-515-server
Reverse-Depends
===
* libnvidia-decode-510-server (for libnvidia-decode-515-server)
* libnvidia-encode-510-server (for libnvidia-encode-515-server)
these too have transitionals via 515-server to 525-server,
About this:
$ reverse-depends src:nvidia-graphics-drivers-460
Reverse-Depends
===
* libnvidia-decode-455 (for libnvidia-decode-460)
* libnvidia-encode-455 (for libnvidia-encode-460)
* nvidia-headless-455 [amd64] (for nvidia-headless-460)
* nvidia-kernel-common-455 [amd64]
Packages
All autopkgtests for the newly accepted linux-meta-hwe-5.15
(5.15.0.94.104~20.04.50) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/245.4-4ubuntu3.22 (armhf)
Please visit the excuses page listed below and investigate the
I ran into this on jammy/amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/amd64/l/livecd-rootfs/20240121_173406_e4f9a@/log.gz
I downloaded all of the amd64 failures and searched for this failure
pattern. These were the kernels that were running at the time:
"Linux
Hello Mathew,
Thanks for responding so promptly.
I did test 6.8-rc1 and ZSWAP works as expected.
But I've noticed something odd.
To quickly test ZSWAP, I use eatmemory tool to allocate 7GB of 8GB on my system.
Allocating worked and ZSWAP activated but freeing 7GB of memory took ~45s
(system
** Summary changed:
- linux-kvm ADT test failure with linux-kvm/5.15.0-1050.55
+ linux-kvm ADT test test_snapd_snap_with_vendored_apparmor failure with
linux-kvm/5.15.0-1050.55
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm
Public bug reported:
This is a scripted bug report about ADT failures while running linux-kvm
tests for linux-kvm/5.15.0-1050.55 on jammy. Whether this is caused by
the dep8 tests of the tested source or the kernel has yet to be
determined.
Testing failed on:
amd64:
A fix is available upstream: https://lore.kernel.org/all/f6e687cc-
debd-4864-901a-fb35be9f2...@kernel.dk/T/
--
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/2049689
Title:
** Changed in: linux-gcp (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-gcp (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-gcp (Ubuntu Bionic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux-gcp (Ubuntu Focal)
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/2042726
Title:
package bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu8 failed to
install/upgrade:
** Tags removed: need-duplicate-check
--
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/204
Title:
package linux-image-6.5.0-10-generic 6.5.0-10.10 failed to
install/upgrade:
** Tags removed: need-duplicate-check
--
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/2044412
Title:
package linux-image-6.2.0-37-generic 6.2.0-37.38 failed to
install/upgrade:
** 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-nvidia-6.2 in
Ubuntu.
https://bugs.launchpad.net/bugs/2045353
Title:
package linux-modules-nvidia-525-6.2.0-1012-nvidia
** 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/2046345
Title:
package linux-modules-nvidia-535-6.5.0-9-generic 6.5.0-9.9 failed
** Tags removed: need-duplicate-check
--
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/2048504
Title:
package linux-headers-6.2.0-39-generic 6.2.0-39.40 failed to
install/upgrade:
** Package changed: ubuntu => bluez (Ubuntu)
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049958
Title:
package bluez-obexd 5.68-0ubuntu1
** Tags removed: need-duplicate-check
--
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/2038508
Title:
package linux-image-6.2.0-34-generic 6.2.0-34.34 failed to
install/upgrade:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to b43-fwcutter in Ubuntu.
https://bugs.launchpad.net/bugs/2040081
Title:
package firmware-b43-installer 1:019-8 failed to install/upgrade:
installed
** 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-hwe-6.2 in
Ubuntu.
https://bugs.launchpad.net/bugs/2042661
Title:
package linux-modules-nvidia-535-6.2.0-36-generic
** Tags removed: need-duplicate-check
--
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/2042078
Title:
package linux-image-6.2.0-36-generic 6.2.0-36.37 failed to
install/upgrade:
** 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-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2042654
Title:
package linux-image-5.15.0-84-generic (not installed) failed to
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2042707
Title:
package nvidia-dkms-470 470.223.02-0ubuntu0.22.04.1 failed to
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2049245
Title:
package nvidia-dkms-390 390.157-0ubuntu0.22.04.2 failed to
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2049688
Title:
nvidia stoped working,, package nvidia-dkms-390
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2049674
Title:
package libnvidia-compute-390 (not installed) failed to
** 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-hwe-6.2 in
Ubuntu.
https://bugs.launchpad.net/bugs/2039363
Title:
package linux-modules-nvidia-535-6.2.0-34-generic
** 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/2043426
Title:
package linux-modules-nvidia-470-5.15.0-82-generic (not installed)
** Tags removed: need-duplicate-check
--
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/2039924
Title:
package linux-image-6.2.0-35-generic 6.2.0-35.35 failed to
install/upgrade:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2043449
Title:
package zfs-dkms 2.1.5-1ubuntu6~22.04.1 failed to install/upgrade:
installed
You have been subscribed to a public bug:
bug found during software update launched from bootable usb
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez-obexd 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules:
** Tags removed: need-duplicate-check
--
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/2045483
Title:
package linux-image-5.15.0-88-generic 5.15.0-88.98 failed to
install/upgrade:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2045969
Title:
package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to
install/upgrade:
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/2049086
Title:
General upgrade to 22.04 leads to second monitor not being
** Tags removed: need-duplicate-check
--
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/2049666
Title:
package linux-image-6.2.0-39-generic 6.2.0-39.40 failed to
install/upgrade:
I narrowed this down a bit further. Last working kernel version is
5.15.0-89-generic. The problem starts to show up with 5.15.0-90-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The verification of the Stable Release Update for systemd 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 encounter a
This bug was fixed in the package systemd - 245.4-4ubuntu3.23
---
systemd (245.4-4ubuntu3.23) focal; urgency=medium
[ Nick Rosbrook ]
* core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File:
Added Package
** Package changed: ubuntu => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2050103
Title:
Integrated Laptop screen not detected on 6.5
Seems like the problem occurs here
```
[2024-01-22T17:13:16.819] [63786.0] cgroup/v2: cgroup_p_constrain_apply:
CGROUP: EBPF Closing and loading bpf program into
/sys/fs/cgroup/system.slice/slurmstepd.scope/job_63786/step_0/user
[2024-01-22T17:13:16.819] [63786.0] error: load_ebpf_prog: BPF
I just noticed that 5.15.0-94.104 is available in jammy-proposed and
tested that. Same problem as with -91
I've enabled debug messages for slurmd with regards to cgroup, log
attached.
** Attachment added: "Slurmd cgroup debug log"
The requested commit (a18615b1cfc0) has the following prerequisite
commit:
f18b1137d38c ("PCI: Extract ATS disabling to a helper function")
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
You have been subscribed to a public bug:
lsb_release
Description:Ubuntu 22.04.3 LTS
Release:22.04
Codename: jammy
Laptop: Rebadged Clevo
Graphics: on-board Intel UHD 630
Updated from kernel 6.2.0-39-generic to 6.5.0-14-generic
Problem:- LCD laptop screen not detected on
rpi-imager currently has no facility to encrypt the image it flashes to
the storage on the Pi (and making such a facility generic enough that it
would fit all potentially interested distros is a daunting task to say
the least), so this isn't valid for rpi-imager.
I *did* add some initial steps
We talked to our systemd maintainer inside foundations and also reached
out to upstream system [1], which didn't lead anywhere. We shouldn't
need to bisect systemd-networkd and do a high impact systemd SRU to fix
a regression in a kernel update, where we can pinpoint the exact (small)
git commit.
** Changed in: fabric-manager-535 (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: libnvidia-nscq-535 (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: nvidia-graphics-drivers-535 (Ubuntu Bionic)
Status: New => Fix Released
** Changed in:
This bug was fixed in the package libnvidia-nscq-535 -
535.154.05-0ubuntu0.22.04.1
---
libnvidia-nscq-535 (535.154.05-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #2048901)
* Make orig tarballs reproducible
-- Dimitri John Ledkov Thu, 11 Jan 2024
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
This bug was fixed in the package fabric-manager-535 -
535.154.05-0ubuntu0.23.10.1
---
fabric-manager-535 (535.154.05-0ubuntu0.23.10.1) mantic; urgency=medium
* New upstream release (LP: #2048901)
* Make orig tarballs reproducible
-- Dimitri John Ledkov Wed, 10 Jan 2024
This bug was fixed in the package libnvidia-nscq-535 -
535.154.05-0ubuntu0.23.10.1
---
libnvidia-nscq-535 (535.154.05-0ubuntu0.23.10.1) mantic; urgency=medium
* New upstream release (LP: #2048901)
* Make orig tarballs reproducible
-- Dimitri John Ledkov Thu, 11 Jan 2024
This bug was fixed in the package nvidia-graphics-drivers-535 -
535.154.05-0ubuntu0.23.10.1
---
nvidia-graphics-drivers-535 (535.154.05-0ubuntu0.23.10.1) mantic; urgency=medium
* New upstream release (LP: #2048901)
* Make orig tarballs reproducible
-- Dimitri John Ledkov Mon,
This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.154.05-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-535-server (535.154.05-0ubuntu0.22.04.1) jammy;
urgency=medium
* New upstream release (LP: #2048901)
* Make orig tarballs reproducible
-- Dimitri John
This bug was fixed in the package nvidia-graphics-drivers-535 -
535.154.05-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-535 (535.154.05-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #2048901)
* Make orig tarballs reproducible
-- Dimitri John Ledkov Mon,
This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.154.05-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-535-server (535.154.05-0ubuntu0.20.04.1) focal;
urgency=medium
* New upstream release (LP: #2048901)
* Make orig tarballs reproducible
-- Dimitri John
This bug was fixed in the package fabric-manager-535 -
535.154.05-0ubuntu0.22.04.1
---
fabric-manager-535 (535.154.05-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #2048901)
* Make orig tarballs reproducible
-- Dimitri John Ledkov Wed, 10 Jan 2024
This bug was fixed in the package nvidia-graphics-drivers-535 -
535.154.05-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-535 (535.154.05-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #2048901)
* Make orig tarballs reproducible
-- Dimitri John Ledkov Mon,
This bug was fixed in the package fabric-manager-535 -
535.154.05-0ubuntu0.20.04.1
---
fabric-manager-535 (535.154.05-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #2048901)
* Make orig tarballs reproducible
-- Dimitri John Ledkov Wed, 10 Jan 2024
Public bug reported:
We're using Slurm workload manager in a cluster with Ubuntu 22.04 and
the linux-generic kernel (amd64). We use cgroups (cgroup2) for resource
allocation with Slurm. With kernel version
linux-image-5.15.0-91-generic 5.15.0-91.101
amd64
I'm seeing a new issue. This
This bug was fixed in the package libnvidia-nscq-535 -
535.154.05-0ubuntu0.20.04.1
---
libnvidia-nscq-535 (535.154.05-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #2048901)
* Make orig tarballs reproducible
-- Dimitri John Ledkov Thu, 11 Jan 2024
I too have this issue:
01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express
Fusion-MPT SAS-2 (rev 05)
Subsystem: Broadcom / LSI 9207-8i SAS2.1 HBA
Kernel driver in use: mpt3sas
Kernel modules: mpt3sas
--
You received this bug notification because you are a member of
My logs simply report the message "kvm: enabling virtualization on CPUx
failed" for each CPU.
No other messages are present.
Could you be interested in my hardware specs?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in
** Also affects: linux (Ubuntu Noble)
Importance: Critical
Status: 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/2028253
Title:
update apparmor and LSM stacking
Can you include some logs so we can properly investigate.
Follow 'Adding debug info to a bug report' from
https://wiki.ubuntu.com/Kernel/Bugs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
Public bug reported:
A vmlinux.h header generated from a kernel build with bpftool is needed to
build and ship BPF CO-RE programs. We are looking to ship these in the next
version of systemd.
vmlinux.h being generated depends on the kernel version, architecture and
kconfig. There are some
The patch is in 6.8-rc1, how can we make Canonical to cherry-pick that
patch into current 6.5 kernel?
--
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/2008583
Title:
VMware nested under
I just tried installing virtualbox dkms and it did build. Version
6.1.48-dfsg-1~ubuntu1.22.04.1.
Are you using a different version?
And some logs from virtualbox client will help.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Information type changed from Private to Public
** Package changed: linux (Ubuntu) => apache2 (Ubuntu)
--
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/2050017
Title:
[24.04 FEAT]
The kernel patch is still in progress but I also wonder if plymouthd
starts early enough to do all the console blocking? If so then it could
FBIOPUT_CON2FBMAP like con2fbmap does, to umap the console from the
framebuffer. But that's still racing with other kernel things which
might have already
This should be solved in the lastest jammy:hwe-6.5 version. It's gonna
be in -proposed these days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048945
Title:
scsi_eh_*
** Tags added: update-excuse
--
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/2049924
Title:
WireGuard broken on Noble ppc64el
Status in linux package in Ubuntu:
New
Status in
For v6.3-rc1 or above, mainline commit 5ae20a8050d08 ("platform/x86:
int3472/discrete: Create a LED class device for the privacy LED")
replaced that sauced patch.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
** Tags added: fixed-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1989046
Title:
support independent clock and LED GPIOs for Intel IPU6 platforms
Status in HWE
** Changed in: linux-xilinx-zynqmp (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu.
https://bugs.launchpad.net/bugs/2049442
Title:
Enable symbols for all
** Changed in: plymouth (Ubuntu)
Status: In Progress => Invalid
--
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
Looks positive on my end, thanks Timo.
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
Verified oem-6.5-1014 on my end with new DMCUB FW(Manually added), I
don't observe this issue happening. We are still waiting for the new
DMCUB FW to be added into linux-firmware for jammy, not sure if we need
one more similar public bug to track FW landing.
I will tag "done" from the patch
98 matches
Mail list logo
