Public bug reported:
While trying to `sudo apt upgrade`, the following error shows up:
Errors were encountered while processing:
/tmp/apt-dpkg-install-E3zKrf/01-libnvidia-gl-535_535.54.03-0ubuntu0.22.04.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType: Package
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Mario, thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2027959
Title:
Follow-up: potential S3 issue for amdgpu Navi 31/Navi33
Status in linux-firmware package in
I've updated the bug description for firmware-sof SRU, and provide the
link to where the firmare is from.
** Description changed:
+ SRU Jusitification for firmware-sof
+
+ [Impact]
+ To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6
+
+ [Fix]
+ Pull sof-bin v2.2.6 and for the
Yes it's on my todo list.
--
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/2025120
Title:
Crash in 6.3.0-7 (ucsi_acpi_async_write [ucsi_acpi]) prevents booting,
while 6.2.0-21 always
Sounds like a kernel bisection is needed?
--
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/2025120
Title:
Crash in 6.3.0-7 (ucsi_acpi_async_write [ucsi_acpi]) prevents booting,
while
As far as I have researched, the Linux patches pointed by Markus haven't
been backported to any of our kernels yet. As such, I am adding a Linux
task to this bug so that the kernel team can chime in and provide some
feedback as to whether these patches will be backported.
@Kernel team, could you
As far as I have researched, the Linux patches pointed by Markus haven't
been backported to any of our kernels yet. As such, I am adding a Linux
task to this bug so that the kernel team can chime in and provide some
feedback as to whether these patches will be backported.
@Kernel team, could you
*** This bug is a duplicate of bug 798414 ***
https://bugs.launchpad.net/bugs/798414
** This bug is no longer a duplicate of bug 1522501
package linux-image-3.13.0-71-generic 3.13.0-71.114 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
return
This affects jammy:linux-oracle-5.15-1040.46 for the 2023.07.10 cycle
The issue is a bit flaky, fails maybe 1/5 times.
** Tags added: sru-20230710
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This affects jammy:linux-oracle-5.15-1040.46 for the 2023.07.10 cycle
** Tags added: sru-20230710
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2006716
Title:
5 failures
Public bug reported:
error trying to update latest driver
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-firmware-535-535.54.03 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
Uname: Linux 5.15.0-67-generic x86_64
NonfreeKernelModules:
Public bug reported:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
linux-tools-5.15.0-76 linux-tools-5.15.0-76-generic linux-tools-common
The following NEW packages will be installed:
** Changed in: linux (Ubuntu Lunar)
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/2026736
Title:
Azure: Fix lockup in swiotlb when used as a
** Tags added: sru-s20230612
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2006716
Title:
5 failures reported in net:fcnal-test.sh on Jammy
Status in ubuntu-kernel-tests:
** Changed in: linux-azure (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Lunar)
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
"@Andreas firmware-sof in Mantic is 2.2.6, which already has everything
in Acelan's merge proposal."
** Changed in: firmware-sof (Ubuntu Mantic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Anthony, I have no preference about 1 vs 2, I only ask that the bug (and
therefore the SRU verification process) be consistent with the upload.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: casper (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Tags removed: verification-needed-lunar
** Tags added: verification-done-lunar
--
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/2018591
Title:
Enable Tracing Configs for OSNOISE and
*** This bug is a duplicate of bug 1532355 ***
https://bugs.launchpad.net/bugs/1532355
** This bug is no longer a duplicate of bug 1547505
package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade:
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
For documentation purposes: the riscv64 build fails on jammy/lunar-proposed,
which is not a regression; that is since/on the jammy/lunar-release pockets.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
You could try newest mainline kernels from [1] to see if that makes it
any better. Note that these are not supported and only for testing and
you need to disable Secure Boot.
[1] https://kernel.ubuntu.com/~juergh/dashboard.html
--
You received this bug notification because you are a member of
Has this worked with older (<5.19) kernel, i.e., is it a regression?
--
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/2006797
Title:
MT7922 firmware not working
Status in linux package
Public bug reported:
vulkaninfo under Wayland fails with:
WARNING: [Loader Message] Code 0 : loader_parse_icd_manifest: Can not find
'ICD' object in ICD JSON file /usr/share/vulkan/icd.d/nvidia_layers.json.
Skipping ICD JSON
ERROR at
** Changed in: linux-bluefield (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/2013383
Title:
mlxbf-bootctl: support
** Changed in: linux-bluefield (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/2016039
Title:
mlxbf-tmfifo: fix
** Changed in: linux-bluefield (Ubuntu Focal)
Status: New => Fix Committed
--
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/2022387
Title:
mlxbf-gige: Fix intermittent no
Attached video of HP Omni 120 Flickering, I tested with kernel 6.0, 6.1,
6.2 (compiled by my self using drm-tip branch), and 6.2 from 23.04, now
testing 6.3, same issue, the only workaround is "nomodeset
i915.modeset=0"
** Attachment added: "HP Omni 120 Flickering"
When all paths are fails multipath -ll or any other command that
accesses those disks ( fdisk , hdparm ) hangs indefinitely until echo 1
> issue_lip is issued
dmesg output after the issue_lip is attached as well
** Attachment added: "dmesg output after issue_lip"
** Attachment added: "multipath -ll -v3 when OK"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2027988/+attachment/5686845/+files/multipath-ll-v3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "lspci output for the mezzanine card"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2027988/+attachment/5686846/+files/lspci-output-host2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
After upgrading an HP BL460 G7 from 20.04 to 22.04, the storage mounted from an
hp msa2324fc using the QLogic QMH2462 dual channel adapter fails all paths
after a while, usually less than an hour.
This occured with kernel 5.15.0-76-generic installed by upgrading, but gave
Public bug reported:
Hello,
First, thank you for maintaining this kernel package for RPi!
When looking at something else[1], Phil Elwell from Raspbian OS noticed
that in the Ubuntu Raspi Lunar image with a kernel v6.2,
CONFIG_MPTCP_IPV6 is not enabled.
I guess this is because CONFIG_IPV6 is
Hi,
on 23.04 again nvidia driver and kernel problems...
had the same issue back in march under 22.10 with funny flickering screens to
total black and back just after an update and therefore a totally unusable
system, and guess? no maintainer showed interest in that messed up situation,
so out
60dc78a70 amdgpu: update GC 11.0.1 firmware for amd.5.5 release
31f8f5269 amdgpu: update GC 11.0.4 firmware for amd.5.5 release
introduced a regression on 11.0.1/11.0.4, which is why specifically
requested (https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/2024427/comments/16) below
** 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/2002226
Title:
Add support for kernels compiled with CONFIG_EFI_ZBOOT
Status in grub2 package in Ubuntu:
Triaged
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux-riscv/6.2.0-27.28.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-lunar' to 'verification-done-lunar'. If the
problem still exists,
This bug is awaiting verification that the linux/6.2.0-27.28 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-27.28 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-27.28 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
This bug is awaiting verification that the linux/6.2.0-27.28 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-lunar' to 'verification-done-lunar'. If the problem
still exists, change
Hello @ihmesa,
We cannot release linux-5.4.0-154.171 anymore, it has been replaced in
-proposed by linux-5.4.0-156.173 which also contains the same fix. We
would appreciate if you could help us test the fix from this version in
-proposed.
Thank you.
--
You received this bug notification
I am removing the duplication of this bug due to the fact that this
requires a separate fix from bug 2015827, and the fix is still applied
and queued for release.
** This bug is no longer a duplicate of bug 2015827
NFS performance issue while clearing the file access cache upon login
--
You
Hello Andreas,
I saw the same error on a 13th Gen Intel(R) Core(TM) i7-1370PE using the
IOT release of jammy desktop.
I can confirm that installing mutter from jammy-proposed fixed the issue
on my system.
$ uname -a
Linux amr-rplp-01 5.15.0-1034-intel-iotg #39-Ubuntu SMP Thu Jun 22 20:56:05 UTC
@Andreas firmware-sof in Mantic is 2.2.6, which already has everything
in Acelan's merge proposal.
@Steve Acelan's merge proposal indeed pulls in 16 new binaries from
upstream's firmware-sof 2.2.5 and 2.2.6, more than this bug originally
need. It's because when we roll out a new HWE kernel in the
I had to run
$ update-maintainer
The original maintainer is: Debian ALSA Maintainers
Resetting as: Ubuntu Developers
after applying the merge debdiff.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
>> Kernels that use u-boot (direct), abootimg, piboot will have to stay
as they are - unless they gain zboot image format boot support.
Hello Dimitri,
zboot kernels are regualr EFI binaries. Where did you see problems in
booting them with U-Boot's bootefi command?
Best regards
Heinrich
--
** Patch added: "0001-UBUNTU-Config-Turn-on-CONFIG_EFI_ZBOOT-on-ARM64.patch"
https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2002226/+attachment/5686814/+files/0001-UBUNTU-Config-Turn-on-CONFIG_EFI_ZBOOT-on-ARM64.patch
** Changed in: linux (Ubuntu)
Importance: Undecided =>
This is resolved correctly in grub2-2.12~rc1. Once that hits mantic, we
will be able to upgrade most of our arm64 kernels to that (generic,
cloud).
Kernels that use u-boot (direct), abootimg, piboot will have to stay as
they are - unless they gain zboot image format boot support.
** Also
Kernel 5.15.0-79.86 from jammy-proposed is verified to fix this bug.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.1 (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
** Description changed:
[impact]
While booting into OOBE, the screen freeze [AMD W7500 only]
[fix]
AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled.
Intel CPU may not support the dynamic lane/speed switching.
- Turn off the dynamic gen/lane switching when
** Description changed:
[impact]
+ While booting into OOBE, the screen freeze [AMD W7500 only]
[fix]
+ AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled.
+ Intel CPU may not support the dynamic lane/speed switching.
+
+ Turn off the dynamic gen/lane switching when
See follow-up in bug 2027959.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2024427
Title:
potential S3 issue for amdgpu Navi 31/Navi33
Status in HWE Next:
New
Status in
make -j8 KERNELRELEASE=6.2.0-24-generic -j8 -C
/lib/modules/6.2.0-24-generic/build
M=/var/lib/dkms/amdgpu/17.40-492261/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.2.0-24-generic (x86_64)
Consult /var/lib/dkms/amdgpu/17.40-492261/build/make.log for more
You have an unsupported DKMS modules installed that prevent the kernel
installation/upgrade. Please remove it and retry:
$ dkms remove amdgpu/17.40-492261 --all
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
You have an unsupported DKMS modules installed that prevent the kernel
installation/upgrade. Remove it and retry:
$ dkms remove rcraid/9.3.0 --all
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You have an unsupported DKMS modules installed that prevent the kernel
installation/upgrade. Remove it and retry:
$ dkms remove rcraid/9.3.0 --all
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
make -C /lib/modules/6.2.0-24-generic/build
M=/var/lib/dkms/rcraid/9.3.0/build/src modules
make[1]: Entering directory '/usr/src/linux-headers-6.2.0-24-generic'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-12 (Ubuntu
@Renjith, @Mario, please help confirm three more commits needed as
listed in bug description.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2027959
Title:
Follow-up: potential
Public bug reported:
Per comment https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/2024427/comments/15 from bug 2024427, more firmware blobs
were requested to be pulled back to linux-firmware/lunar and jammy. They
are:
* ffe1a41e2 amdgpu: update GC 11.0.0 firmware for amd.5.5
It appears the nvidia driver doesn't support kernel 6.5 yet. This isn't
really an Ubuntu bug since Ubuntu doesn't support it officially yet
either.
nv-mm.h:88:16: error: too many arguments to function
‘get_user_pages’
** Changed in: nvidia-graphics-drivers-525 (Ubuntu)
Status: New =>
Public bug reported:
[impact]
[fix]
[test cases]
1. boot with w7500
2. the screen doesn't freeze and can't find the error message in dmesg.
"amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out"
[where the issue could happen]
** Affects: linux (Ubuntu)
Importance: Undecided
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dkms (Ubuntu)
Status: New => Confirmed
--
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/2027634
>From the daily runs on images I can see that 6.2.0-1008 seems to be fixed in
>that regard.
It loses just as much as it formerly gained.
Since this arrived in lunar-updates/security should we close this bug?
--
You received this bug notification because you are a member of Kernel
Packages,
83 matches
Mail list logo
