I can see the fix coming to Plucky in 6.12.0-10.10 now.
** Also affects: linux via
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12160
Importance: Unknown
Status: Unknown
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug noti
** Also affects: linux-lowlatency-hwe-6.8 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-lowlatency-hwe-6.8 (Ubuntu Focal)
** No longer affects: linux-lowlatency-hwe-6.8 (Ubuntu Noble)
** No longer affects: linux-lowlatency-hwe-6.8 (Ubuntu Oracular)
** No longe
Thanks for verifying Oracular Till!
** Tags added: verification-done-oracular-linux
--
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/2084046
Title:
[i915] Phantom "Unknown" display detect
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
This bug is awaiting verification that the linux-
nvidia-6.11/6.11.0-1003.3 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-noble-linux-nvidia-6.11' to
'verification-done-noble-linux-n
Hi Brett,
The Cert requirements are hitting 80% of advertised line rate which is
largely passable even on noisy networks absent issues with drivers or
firmware causing performance issues. In most cases, devices hit 95+
percent so 80 is typically a low bar to meet, but we do occasionally hit
cases
As another data point, we're seeing this bug on one of our NFS servers
running Ubuntu 24.04.1 with 6.8.0-51 kernel. Also experienced a similar
issue to one of the above users with unable to start nfs-kernel-server
and trying to restart the service.
[2164406.282362] INFO: task nfsd:8039 blocked fo
@mruffell, thank you very much!
I have installed the kernel 6.11.0-17-generic on my Oracular system now
and the ghost screen has gone away. All perfect now for me. Now I should
be able to do projections on conferences in Mirror mode without
problems.
$ uname -rv
6.11.0-17-generic #17-Ubuntu SMP P
Public bug reported:
package linux-firmware 20240913.gita34e7a5f-0ubuntu2.2 [modified:
lib/firmware/amdgpu/renoir_vcn.bin.zst
lib/firmware/amdgpu/sienna_cichlid_rlc.bin.zst] failed to
install/upgrade: unable to stat
'./lib/firmware/cxgb3/ael2005_opt_edc.bin.zst' (which was about to be
installed):
Hi everyone,
I have excellent news. The Kernel Team respun this current SRU cycle to include
more patches, and
commit ad604f0a4c040dcb8faf44dc72db25e457c28076
Author: Thomas Zimmermann
Date: Tue Sep 24 10:41:03 2024 +0200
Subject: firmware/sysfb: Disable sysfb for firmware buffers with unknown p
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Mehmet Basaran (mehmetbasaran)
--
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/2050083
Title:
generate and ship vmlinux.
This bug was fixed in the package alsa-ucm-conf - 1.2.10-1ubuntu5.4
---
alsa-ucm-conf (1.2.10-1ubuntu5.4) noble; urgency=medium
* Add codec Realtek rt722 and rt1320 support (LP: #2086250)
- d/p/0001-ucm2-soundwire-add-rt722-SDCA-device.patch
- d/p/0002-sof-soundwire-fix-miss
This bug was fixed in the package alsa-ucm-conf - 1.2.10-1ubuntu5.4
---
alsa-ucm-conf (1.2.10-1ubuntu5.4) noble; urgency=medium
* Add codec Realtek rt722 and rt1320 support (LP: #2086250)
- d/p/0001-ucm2-soundwire-add-rt722-SDCA-device.patch
- d/p/0002-sof-soundwire-fix-miss
This bug was fixed in the package alsa-ucm-conf - 1.2.10-1ubuntu6.3
---
alsa-ucm-conf (1.2.10-1ubuntu6.3) oracular; urgency=medium
* Add codec Realtek rt722 and rt1320 support (LP: #2086250)
- d/p/0001-ucm2-soundwire-add-rt722-SDCA-device.patch
- d/p/0002-sof-soundwire-fix-m
The verification of the Stable Release Update for alsa-ucm-conf 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 encou
This bug was fixed in the package alsa-ucm-conf - 1.2.10-1ubuntu6.3
---
alsa-ucm-conf (1.2.10-1ubuntu6.3) oracular; urgency=medium
* Add codec Realtek rt722 and rt1320 support (LP: #2086250)
- d/p/0001-ucm2-soundwire-add-rt722-SDCA-device.patch
- d/p/0002-sof-soundwire-fix-m
** Description changed:
+ SRU Justification
+
+ [Impact]
+
+ * Seeing crash due to use-after-free. Logs included below SRU
+ justification
+
+ [Fix]
+
+ * Backport 38c0324c0fb6: "Linux: Fix zfs_prune panics"
+
+ [Test Plan]
+
+ * Compile tested
+ * Run through autopkgtest regression tests
+
** Changed in: linux-lowlatency (Ubuntu Noble)
Importance: Undecided => Low
** Changed in: linux-lowlatency (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: linux-lowlatency (Ubuntu Noble)
Assignee: (unassigned) => Mehmet Basaran (mehmetbasaran)
--
You received this bug
Public bug reported:
tracking bug
** Affects: zfs-linux (Ubuntu)
Importance: High
Assignee: Heitor Alves de Siqueira (halves)
Status: In Progress
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member
This bug is awaiting verification that the linux-oem-6.8/6.8.0-1020.20
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-noble-linux-oem-6.8' to 'verification-done-
noble-linux-oem-6.8'.
Yes it's easy as putting something in fullscreen, but as mentioned
earlier when I tried to get solid STR to make sure I could give a
straight answer whether it fixes, then I had difficulties. At some point
it reproduced but I don't know why at that moment I hit it.
So anything that I need to test
Including 2.2.6-1ubuntu1.1.debdiff for updates.
** Patch added: "2.2.6-1ubuntu1.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2077926/+attachment/5853510/+files/2.2.6-1ubuntu1.1.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, w
** Description changed:
+ SRU Justification
+
+ [Impact]
+
+ * Having occurrences of "detected field-spanning write" on zpool import.
+ Logs included below SRU justification
+
+ [Fix]
+
+ * Backport 6f50f8e16b7c: "zfs_log: add flex array fields to log record
structs"
+ * Backport c84a37ae93b5
** Also affects: zfs-linux (Ubuntu Oracular)
Importance: Undecided
Status: New
--
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/2082060
Title:
memcpy: detected field-spanning
** Also affects: zfs-linux (Ubuntu Noble)
Importance: Undecided
Status: New
--
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/2077926
Title:
crash in openzfs - 2.2.2 not suppo
> I clearly dont have time to play with (1) and rebuilding/maintaining a
kernel in the hope of a non reproduction ; especially since I dont have
clear STR so it means making this my daily driver.
I'm not suggesting you to keep using/maintaining such a kernel, it's a
debugging data point to prove w
The bug was reported on Noble and the fix was ported to Oracular for
good measure. maxgl reported verification-done-noble-linux so I also
report verification-done-oracular-linux because of the triviality of the
patch.
** Tags removed: verification-needed-noble-linux
verification-needed-oracular-l
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
I clearly dont have time to play with (1) and rebuilding/maintaining a
kernel in the hope of a non reproduction ; especially since I dont have
clear STR so it means making this my daily driver.
That leaves only (2). Does this DRM debug enabling have an impact on
perf / features ? For the same reas
>From the trace this is triggered from a userspace IOCTL to remove a
framebuffer. This causes drm core to process atomic_remove_fb() as
work, and this will use the drm driver to do atomic modesets.
One of the things that happens for this is going to be recalculating MST
DSC configs (if appropriat
Public bug reported:
Attempted to download nvidia drivers from software center because when
running nvidia-smi in terminal, got an error telling me that it couldn't
communicate with the nvidia driver and that I should update it.
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: nvidia-dkm
verified pass on linux-mtk 1036 kernel.
check the sound card still existed after rebooting with dpoc
disconnected.
** Tags removed: verification-needed-jammy-linux-mtk
** Tags added: verification-donejammy-linux-mtk
** Tags removed: verification-donejammy-linux-mtk
** Tags added: verification-d
** Also affects: linux-lowlatency (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-lowlatency (Ubuntu Oracular)
Status: New => Fix Committed
** Changed in: linux-lowlatency (Ubuntu Oracular)
Assignee: (unassigned) => Koichiro Den (koichiroden)
** Changed in:
Filed dracut upstream bug https://github.com/dracut-ng/dracut-
ng/issues/1150 and launchpad bug 2095518.
** Bug watch added: github.com/dracut-ng/dracut-ng/issues #1150
https://github.com/dracut-ng/dracut-ng/issues/1150
--
You received this bug notification because you are a member of Kernel
** Also affects: linux-ibm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-ibm (Ubuntu Plucky)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-ibm in Ubuntu.
https://bugs
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.7
---
linux-firmware (20240318.git3b128b60-0ubuntu2.7) noble; urgency=medium
* Intel(R) Wi-Fi 7 BE201 320MHz: Direct firmware load for
iwlwifi-bz-b0-gf-a0-*.ucode failed with error -2 (LP: #2085547)
The verification of the Stable Release Update for linux-firmware 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 enco
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.7
---
linux-firmware (20240318.git3b128b60-0ubuntu2.7) noble; urgency=medium
* Intel(R) Wi-Fi 7 BE201 320MHz: Direct firmware load for
iwlwifi-bz-b0-gf-a0-*.ucode failed with error -2 (LP: #2085547)
This bug was fixed in the package linux-firmware -
20240913.gita34e7a5f-0ubuntu2.4
---
linux-firmware (20240913.gita34e7a5f-0ubuntu2.4) oracular; urgency=medium
* Add AMD Navi44/48 support (LP: #2092225)
- amdgpu: update dmcub 0.0.246.0 firmware
linux-firmware (20240913.gita34e
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.7
---
linux-firmware (20240318.git3b128b60-0ubuntu2.7) noble; urgency=medium
* Intel(R) Wi-Fi 7 BE201 320MHz: Direct firmware load for
iwlwifi-bz-b0-gf-a0-*.ucode failed with error -2 (LP: #2085547)
The verification of the Stable Release Update for linux-firmware 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 enco
This bug was fixed in the package linux-firmware -
20240913.gita34e7a5f-0ubuntu2.4
---
linux-firmware (20240913.gita34e7a5f-0ubuntu2.4) oracular; urgency=medium
* Add AMD Navi44/48 support (LP: #2092225)
- amdgpu: update dmcub 0.0.246.0 firmware
linux-firmware (20240913.gita34e
This bug was fixed in the package linux-firmware -
20240913.gita34e7a5f-0ubuntu2.4
---
linux-firmware (20240913.gita34e7a5f-0ubuntu2.4) oracular; urgency=medium
* Add AMD Navi44/48 support (LP: #2092225)
- amdgpu: update dmcub 0.0.246.0 firmware
linux-firmware (20240913.gita34e
The verification of the Stable Release Update for linux-firmware 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 enco
It currently seems also like 6.8.0-51 on 22.04 started to display
internal display as two displays (monitors.xml shows None-1 and eDP-1)
which causes all kinds of mischief. I don't currently have direct access
to it however.
--
You received this bug notification because you are a member of Kernel
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-6.8 (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.8 in Ubuntu.
https://bug
** Also affects: linux-lowlatency (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Noble)
Importance: Undecided
Status: New
** No longer affects: linux-lowlatency (Ubuntu Noble)
** No longer affects: linux-raspi (Ubuntu Noble)
--
You rec
** Also affects: linux-lowlatency (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2095402
Title:
linux-raspi: add dwarfdump pack
Patch was submitted to the Ubuntu kernel team mailing list for noble:
https://lists.ubuntu.com/archives/kernel-team/2025-January/thread.html#156470
Changing status to 'In Progress'.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-power-systems
Importance: U
Successful kernel test builds are available in this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp2077722
--
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/2077722
Title:
[Ubuntu 24
In source code for /usr/lib/dracut/dracut-install, that is, source
package dracut, file src/install/dracut-install.c, function
install_firmware:
_asprintf(&fwpath, "%s/%s", *q, value);
if (strpbrk(value, "*?[") != NULL
&& access(fwpath, F_OK) != 0) {
size_t i;
_clean
The error doesn't affect functionality.
There is no driver changes since 6.11 to 6.13.
Please also file an upstream bug.
--
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/2091073
Title:
SP
Somehow I feel there is a bug in update-initramfs.
So after install custom blobs:
$ ls -l|awk '/->/ {print $9 " " $10 " " $11}'
ish_lnlm_39ceeaf8_0f095bd1.bin.zst -> ish_lnlm_39ceeaf8_58.7724.2.bin.zst
ish_lnlm_39ceeaf8_27e280ea.bin.zst -> ish_lnlm_39ceeaf8_58.7724.2.bin.zst
ish_lnlm_39ceeaf8_2d9
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * L2 guest(s) (nested virtualization) running stress-ng getting stuck
+at booting after triggering crash.
+
+ * When for example having two Ubuntu 24.04 guests and running
+stress-ng (90% load) on both
** Also affects: nvidia-graphics-drivers-535 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- New upstream release 535.230.02 ERD13
+ New upstream release 535.230.02 ERD13/UDA 14
** Summary changed:
- New upstream release 535.230.02 ERD13/UDA 14
+ New upstream release
Same Problem here,
please fix that bug, thank you.
HW: Ubuntu 24.04 on am Lenovo Thinkpad X13 (PSREF: 20W80013GE) Intel
i5-11357G7
I appreciate Ubuntu a lot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
I think the firmware-sof are [1][2], but IIRC they had been in -proposed
firmware-sof by the time I was working on this. Can't remember which
exact version they were SRUed so I just install the -proposed one
blindly.
[1]
https://github.com/thesofproject/sof-bin/blob/main/v2.11.x/sof-ipc4-tplg-v2.
which proposed firmware-sof does this need? it's not mentioned or linked
here
the current sru of firmware-sof has only 2093077 which doesn't seem
related?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Hi Paolo,
I tried the new kernel, and find it still could trigger the cpu_lockup
several times during my 20 reboot cycle, I will upload the log for your
review.
Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
** Changed in: linux-oem-6.8 (Ubuntu Noble)
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/2091077
Title:
UBSAN: array-index-out-of-bounds in
** Attachment added: "dmesg_log.zip"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081685/+attachment/5853345/+files/dmesg_log.zip
--
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
$ find /lib/modules/$(uname -r) -name \*.ko.zst -exec bash -c "m=\$(basename
"{}"); m=\${m%%.*}; modinfo \$m|grep '^firmware:.*\*'" \;
firmware: brcm/brcmbt4388*.ptb
firmware: brcm/brcmbt4388*.bin
firmware: brcm/brcmbt4387*.ptb
firmware: brcm/brcmbt4387*.bin
firmware:
It looks like this is causing at least some instances of bug 2095456.
--
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/2084046
Title:
[i915] Phantom "Unknown" display detected on Intel Met
All autopkgtests for the newly accepted linux-meta-hwe-6.11
(6.11.0-17.17~24.04.2) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
dkms/unknown (amd64)
dpdk-kmods/unknown (amd64, arm64)
fwts/unknown (amd64, arm64)
lxc/unknown (amd64
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => AaronMa (mapengyu)
--
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/2093390
Title:
ThinkBook 14+ GXTP5100 Touchpad Movement Not
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => AaronMa (mapengyu)
--
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/2091073
Title:
SPD5118 DDR5 temperature sensor errors on Th
Boot test done on linux-xilinx/6.8.0-1011.12 kernel.
QA had also ran automated test without finding any new bugs.
Change tag to 'verification-done-noble-linux-xilinx'.
** Tags removed: verification-needed-noble-linux-xilinx
** Tags added: verification-done-noble-linux-xilinx
--
You received this
** No longer affects: linux-xilinx-zynqmp (Ubuntu)
** No longer affects: linux-xilinx-zynqmp (Ubuntu Noble)
** Changed in: linux-xilinx (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xi
** Also affects: linux-xilinx (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-xilinx (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: linux-xilinx-zynqmp (Ubuntu Noble)
Status: Fix Committed => Invalid
** No longer affects: linux-xilinx-zynqmp (U
I've re-run the tests against the proposed kernel and no longer see
these warnings. Thanks for taking the patches to fix this!
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
You received this bug notification because you are a member of Kernel
P
All autopkgtests for the newly accepted linux-restricted-modules-azure-nvidia
(6.8.0-1009.9) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-525/unknown (arm64)
nvidia-graphics-drivers-525-server/unknown (arm
** Also affects: linux-oem-6.11 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.11 (Ubuntu Plucky)
Status: New => Fix Committed
** Changed in: linux-oem-6.11 (Ubuntu Oracular)
Status: New => Invalid
** Changed in: linux-oem-6.11 (Ubuntu Noble)
Could you please provide logs and more detailed information about your
issue?
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/
Fix confirmed for 6.8.0-53 (tested on Noble):
# uname -a
Linux max-laptop 6.8.0-53-generic #55-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 17
15:37:52 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/os-release
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.1 LTS (Noble Numbat)"
VERSION_CODENAME=noble
96 matches
Mail list logo
