Building module:
Cleaning build area...
'make' -j12 KDIR=/lib/modules/6.5.0-21-generic/build modules
MODULE_VERSION=2023.11.1-36...(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/intel-platform-cse-dkms.0.crash'
Error! Bad return status for module build on ke
** Changed in: oem-priority
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/2049838
Title:
Mute/mic LEDs no function on HP ZBook
Status
You have a broken/unsupported DKMS module installed that breaks the
kernel header installation. Remove it.
$ dkms remove intel-platform-cse-dkms/2023.11.1-36
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kern
Building module:
Cleaning build area...
'make' -j8 KVER=6.5.0-21-generic
KSRC=/lib/modules/6.5.0-21-generic/build...(bad exit status: 2)
ERROR (dkms apport): binary package for 8812au: 5.6.4.2_35491.20191025 not found
Error! Bad return status for module build on kernel: 6.5.0-21-generic (x86_6
Unsupported DKMS breaks the kernel header installation Remove it.
$ dkms remove 8812au/5.6.4.2_35491.20191025
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
This seems to have been an update publication issue in a version of
Ubuntu that is no longer supported (14.10), I don't think there is bug
described here that still exists.
I am setting this to "Incomplete" to give some time for anyone to
confirm being affected by this, I am also downgrading sever
--- Comment From s...@de.ibm.com 2024-02-26 03:48 EDT---
Ubuntu noble 24.04 is using glibc 2.39 which includes the required patch:
> In glibc-upstream, this configure check is now adjusted and it allows
> checking binutils by version number:
> commit "s390x: Fix static PIE condition for to
Removing packages from noble:
linux-headers-raspi 6.5.0.1005.6 in noble armhf
linux-headers-raspi-nolpae 6.5.0.1005.6 in noble armhf
linux-image-raspi 6.5.0.1005.6 in noble armhf
linux-image-raspi-nolpae 6.5.0.1005.6 in noble armhf
linux-modules-extra-raspi 6
hi,
In which kernel series you're interested in?
Focal, jammy, mantic, noble?
Please update the ticket to reflect it.
Click on 'Target to series'
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
https://access.redhat.com/articles/7011459
--
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/2053049
Title:
cppc_cpufreq.ko doesn't load on Cavium ThunderX2 system w/Ubuntu
22.04.3 LTS
S
** Description changed:
Sru justification
[Impact]
- Upstream v5.15.139 (#lp2049432) brought commit "selftests/bpf: Test tail
call counting with bpf2bpf and data on stack" that affects one of the bpf
kselftests.
+ Upstream v5.15.139 (#lp2049432) brought commit "selftests/bpf: Test tail
This bug was fixed in the package linux-raspi - 6.7.0-1001.1
---
linux-raspi (6.7.0-1001.1) noble; urgency=medium
* noble/linux-raspi: 6.7.0-1001.1 -proposed tracker (LP: #2051136)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update updat
This bug was fixed in the package linux-raspi - 6.7.0-1001.1
---
linux-raspi (6.7.0-1001.1) noble; urgency=medium
* noble/linux-raspi: 6.7.0-1001.1 -proposed tracker (LP: #2051136)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update updat
This bug was fixed in the package linux-raspi - 6.7.0-1001.1
---
linux-raspi (6.7.0-1001.1) noble; urgency=medium
* noble/linux-raspi: 6.7.0-1001.1 -proposed tracker (LP: #2051136)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update updat
This bug was fixed in the package linux-raspi - 6.7.0-1001.1
---
linux-raspi (6.7.0-1001.1) noble; urgency=medium
* noble/linux-raspi: 6.7.0-1001.1 -proposed tracker (LP: #2051136)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update updat
This bug was fixed in the package linux-raspi - 6.7.0-1001.1
---
linux-raspi (6.7.0-1001.1) noble; urgency=medium
* noble/linux-raspi: 6.7.0-1001.1 -proposed tracker (LP: #2051136)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update updat
This bug was fixed in the package linux-raspi - 6.7.0-1001.1
---
linux-raspi (6.7.0-1001.1) noble; urgency=medium
* noble/linux-raspi: 6.7.0-1001.1 -proposed tracker (LP: #2051136)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update updat
This bug was fixed in the package linux-raspi - 6.7.0-1001.1
---
linux-raspi (6.7.0-1001.1) noble; urgency=medium
* noble/linux-raspi: 6.7.0-1001.1 -proposed tracker (LP: #2051136)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update updat
This bug was fixed in the package linux-raspi - 6.7.0-1001.1
---
linux-raspi (6.7.0-1001.1) noble; urgency=medium
* noble/linux-raspi: 6.7.0-1001.1 -proposed tracker (LP: #2051136)
* Packaging resync (LP: #1786013)
- [Packaging] update Ubuntu.md
- [Packaging] update updat
This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.154.05-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-535-server (535.154.05-0ubuntu0.20.04.2) focal;
urgency=medium
* Install all ABI builds of the libnvidia-pkcs11 plugin for host/container
compatibility.
This bug was fixed in the package nvidia-graphics-drivers-535-server -
535.154.05-0ubuntu0.22.04.2
---
nvidia-graphics-drivers-535-server (535.154.05-0ubuntu0.22.04.2) jammy;
urgency=medium
* Install all ABI builds of the libnvidia-pkcs11 plugin for host/container
compatibility.
Hi Robert! Thanks for testing this on jammy. I marked the tag as verified
('verification-done-jammy-linux') to reflect that.
Could you share the results from mantic? we need to release this next week and
we need a confirmation this works as expected.
If your test looks fine, please remove 'verifi
Hi Roxana,
I'm confused by your comment #11. You write about versions
6.5.0-21.21~22.04.1 and 6.5.0-25.25~22.04.1. Do both contain the fix?
As of today, I can see neither of these versions, but only
6.5.0.21.21~22.04.11 (.11, not .1!). And that version has already been
released as a regular (not
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2054845
Title:
mlxbf-gige: support fi
I built arm64 pi kernel, and installed it to my raspi 4 board
successfully.
** Tags removed: verification-needed-jammy-linux-raspi
** Tags added: verification-done-jammy-linux-raspi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** 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/2052980
Title:
Azure: cif
** 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/2052723
Title:
Azure: Ena
Yes, both contain the fix. We run two cycles in parallel (one for security that
releases earlier nd contains critical fixes (mostly CVEs) and then the sru
cycle that is released 2 weeks after.
This seemed critical and we decided to include in the security cycle so it will
reach end users 2 weeks
Public bug reported:
* intro
As IDR can't protect itself from the concurrent modification, place
idr_remove() under the protection of tp->lock.
* how to fix
need to backport the patch from Jianbo
"net/sched: flower: Add lock protection when remove filter handle"
https://git.kernel.org/pub/scm/lin
Bump. Is anyone looking at this at all?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048945
Title:
scsi_eh_* process using idle CPU after upgrade to kernel 6.5
Status in linu
It seems as I found a permanent fix. In case anyone having the same
issue, this approach fixed it for me:
1. Unpair the mouse in Windows, i.e. delete it inside the Bluetooth settings.
This will delete the respective keys in the Windows registry, too.
2. Unpair the mouse in Ubuntu, i.e. revoke the
Public bug reported:
Coresight PMU driver didn't reject events meant for other PMUs.
This caused some of the Core PMU events disappearing from
the output of "perf list". In addition, trying to run e.g.
$ perf stat -e r2 sleep 1
made Coresight PMU driver to handle the ev
Public bug reported:
[ 1918.995157] watchdog: BUG: soft lockup - CPU#0 stuck for 1725s! [kswapd0:42]
[ 1919.002366] Modules linked in: raid10 raid456 libcrc32c async_raid6_recov
async_memcpy async_pq async_xor xor xor_neon async_tx raid6_pq raid1 raid0
multipath linear scsi_dh_alua scsi_dh_emc s
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
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
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
Public bug reported:
[Impact]
The GPU Direct over Infiniband feature of NVIDIA GPUs no longer works on
jammy/hwe kernels that have migrated to 6.5 *except* for the -nvidia kernel,
which pulled in support via bug 2049537.
We have carried this patch since 5.4 (see bug 1923104). We do not plan
to
** Description changed:
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 originat
Public bug reported:
[Impact]
When producing a new version of some kernels, we need to check for
changes that might affect FIPS certs and justify why a commit was kept.
Currently there is a fips-check script that complains whenever a commit
with crypto-related changes is found without any justif
So i reported the bug for you. But my computer is still in the same bad
shape. Will the new kernel fix it? Or will I have to format and
reinstall ubuntu again?
Em 30/01/2024 01:34, Daniel van Vugt escreveu:
> Oh I missed that. Having a problem with recovery mode probably means
> this isn't as si
Public bug reported:
SRU Justification:
[Impact]
The BlueField-2 and BlueField-3 silicon designs include a
provision for reporting pause frame counters, but the driver
(mlxbf_gige) does not have software support yet.
[Fix]
The fix is to update the mlxbf_gige driver to support the
"get_pause_st
I can confirm that the mqueue patches are present in linux-xilinx-
zynqmp: commits 6e7ff802c7b10 and b4ebbcfebd4d3
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp
** Tags added: verification-done-jammy-linux-xilinx-zynqmp
--
You received this bug notification because you are a mem
** 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.
https://bugs.launchpad.net/bugs/2054487
Title:
There
I suggest you keep using older kernels for the time being. Please also
subscribe to bug 2028165 because that does seem to be happening on your
system.
--
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.la
All autopkgtests for the newly accepted linux-meta-oracle (5.4.0.1119.112) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/245.4-4ubuntu3.23 (arm64)
Please visit the excuses page listed below and investigate the failures,
Find the problem, it isn't a broken/unsupported DKMS module for my case.
The system's default gcc/g++ version is 13. While installing CUDA 11.8,
I used update-alternatives to change the gcc/g++ version to 11. Switch
back to gcc/g++ 13 solved this issue.
--
You received this bug notification beca
You have been subscribed to a public bug:
Hello,
I recently installed Ubuntu 22.04.4 on a Lenovo V145-15AST laptop.
Randomly, the screen will start flickering. I have found that pulling
the power cable out sometimes solves the issue ! But even so, with the
power cable out the screen can still sta
I have done my typical CUDA based testing with this package using the
generic, nvidia and gcp kernels using bionic, focal, jammy and mantic
(amd64 only so far).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in
By the way, there's a typo in:
1915.enable_psr=0
which would usually be:
i915.enable_psr=0
but even that won't help here because you have AMD graphics, not Intel.
The equivalent workaround for AMD graphics is:
amdgpu.dcdebugmask=0x10
so please try that.
** Changed in: linux-hwe-6.5 (U
There are lots of amdgpu errors in your system log, so let's start
there.
** Tags added: amdgpu
** 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.
https://
Changes have been landed under tag 20230919.git3672ccab-0ubuntu2.6, and
verified in 20230919.git3672ccab-0ubuntu2.8, which is lately respined as
20230919.git3672ccab-0ubuntu2.9 with no additional change made.
--
You received this bug notification because you are a member of Kernel
Packages, which
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1080.76)
for focal have finished running.
The following regressions have been reported in tests triggered by the package:
acpi-call/unknown (arm64)
ddcci-driver-linux/unknown (arm64)
dm-writeboost/unknown (arm64)
dpdk/unknown (ar
Private bug reported:
Description: [DELL Ubuntu 22.04.3] observing "UEFI0074 The Secure Boot
policy has been modified since the last time the system was started."
logs in LC. Loaded X.509 cert 'Canonical Ltd. Secure Boot Signing in
dmesg.
Version-Release
ubuntu 22.04.3, 24.04.4
Steps to Reprod
LifeCycle controller logs
---
UEFI0074-The Secure Boot policy has been modified since the last time the
system was started.
Detailed Description:
The system BIOS logs this message after detecting a change in Secure Boot
policy settings. Such a change may result
is this the expected behavior from ubuntu when we do bios reset to
default and clear NVRAM ???
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Thanks for the clarification! I'm running 6.5.0-21-generic #21~22.04.1
now. I'll report if the problem occurs again (in my usage it happened
every one or two days).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ub
56 matches
Mail list logo
