[Kernel-packages] [Bug 2094270] [NEW] Bring in some 6.8 CONFIG annotations that were missed
Public bug reported:
CONFIG_CORESIGHT_TRBE policy<{'arm64': 'm'}>
CONFIG_CORESIGHT_TRBE note<'Required for Grace
enablement'>
+CONFIG_PREEMPT_NONE policy<{'amd64': 'n', 'arm64':
'y'}>
+CONFIG_PREEMPT_NONE note<'Required for NVIDIA
workloads'>
+
+CONFIG_PREEMPT_VOLUNTARYpolicy<{'amd64': 'y', 'arm64':
'n'}>
+CONFIG_PREEMPT_VOLUNTARYnote<'Required for NVIDIA
workloads'>
+
+CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMANDpolicy<{'arm64': 'n'}>
+CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMANDnote<'Required for NVIDIA
workloads'>
+
+CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE policy<{'amd64': 'n', 'arm64':
'y'}>
+CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE note<'Required for NVIDIA
workloads'>
+
CONFIG_DRM_NOUVEAU policy<{'amd64': 'n', 'arm64':
'n'}>
CONFIG_DRM_NOUVEAU note<'Disable nouveau for
NVIDIA kernels'>
** Affects: linux-nvidia-6.11 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2094270
Title:
Bring in some 6.8 CONFIG annotations that were missed
Status in linux-nvidia-6.11 package in Ubuntu:
New
Bug description:
CONFIG_CORESIGHT_TRBE policy<{'arm64': 'm'}>
CONFIG_CORESIGHT_TRBE note<'Required for Grace
enablement'>
+CONFIG_PREEMPT_NONE policy<{'amd64': 'n',
'arm64': 'y'}>
+CONFIG_PREEMPT_NONE note<'Required for NVIDIA
workloads'>
+
+CONFIG_PREEMPT_VOLUNTARYpolicy<{'amd64': 'y',
'arm64': 'n'}>
+CONFIG_PREEMPT_VOLUNTARYnote<'Required for NVIDIA
workloads'>
+
+CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMANDpolicy<{'arm64': 'n'}>
+CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMANDnote<'Required for NVIDIA
workloads'>
+
+CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE policy<{'amd64': 'n',
'arm64': 'y'}>
+CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE note<'Required for NVIDIA
workloads'>
+
CONFIG_DRM_NOUVEAU policy<{'amd64': 'n',
'arm64': 'n'}>
CONFIG_DRM_NOUVEAU note<'Disable nouveau for
NVIDIA kernels'>
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.11/+bug/2094270/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2093379] Re: package libnvidia-compute-390 (not installed) HP prolient ML 110 G9
*** This bug is a duplicate of bug 2049674 *** https://bugs.launchpad.net/bugs/2049674 ** This bug has been marked a duplicate of bug 2049674 package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 -- 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/2093379 Title: package libnvidia-compute-390 (not installed) HP prolient ML 110 G9 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: HP Prolient ML110 G9 8GB Ubuntu 20.04.6 Second video card Graphics: Device-1: NVIDIA GF106GL [Quadro 2000] driver: nvidia v: 390.157 Display: x11 server: X.Org 1.20.13 driver: modesetting,nouveau unloaded: fbdev,vesa resolution: 1600x900~60Hz OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 21.2.6 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-390 (not installed) ProcVersionSignature: Ubuntu 5.15.0-130.140~20.04.1-generic 5.15.168 Uname: Linux 5.15.0-130-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 10 07:39:54 2025 ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 InstallationDate: Installed on 2025-01-08 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2093379/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2089207] Re: firmware files for the Cirrus CS35L54 and CS35L56 codecs
** Tags added: jira-stella-440 oem-priority stella -- 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/2089207 Title: firmware files for the Cirrus CS35L54 and CS35L56 codecs Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Noble: Fix Released Status in linux-firmware source package in Oracular: Fix Released Bug description: [Impact] Audio output doesn't work on HP platforms with CS35L54 and CS35L56 speaker amplifiers [Fix] This requires following firmware blobs: a6f3ab98 cirrus: cs35l56: Update firmware for Cirrus Amps for some HP laptops 6f4db449 cirrus: cs35l56: Add firmware for Cirrus Amps for some HP laptops To fix the WHENCE conflict(noble only), cherry pick one more commit d3a655e2 cirrus: cs35l56: Add firmware for Cirrus CS35L56 for various ASUS laptops [Test] 1. Boot up the machine of HP platform with CS35L54 or CS35L56 speaker 2. Verify with checking the output of `aplay -l` command with valid sof output device. Should never be dummy output. [Where problems could occue] Those are all new files for CS35L54 and CS35L56 amplifier. Should be low low risk of regression To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2089207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2081685] Re: [Ubuntu 24.04-generic Kernel-6.8]Hard lockup on 8 Socket System, ThinkSystem SR950 V3.
Hi Amy, sorry for the delay. Here's another kernel for you to test: https://people.canonical.com/~ppisati/lp2081685/e72dddad462d.2/ It's a clone of e72dddad462d, built with a slightly different toolchain. Let me how it goes. -- 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/2081685 Title: [Ubuntu 24.04-generic Kernel-6.8]Hard lockup on 8 Socket System, ThinkSystem SR950 V3. Status in linux package in Ubuntu: New Status in linux source package in Noble: In Progress Status in linux source package in Oracular: New Bug description: There is CPU hard Lockup detected under Ubuntu 24.04 LTS (kernel 6.8.0-38). see attachment"dmesg0723-Lockup-Ubuntu24.04.log" ubuntu@SR950V3:~$ cat /var/log/dmesg | grep -i lockup [ 15.241164] kernel: watchdog: Watchdog detected hard LOCKUP on cpu 124 [ 15.241164] kernel: ? watchdog_hardlockup_check+0x1cb/0x3b0 Besides, the issue does not occur on upstream kernel 6.8，6.9, 6.10, 6.11-rc*, then only ubuntu kernel issue. see attachment "dmesg0923-No-Lockup-Kernel 6-10.log". According to the dmesg log, the "hard lockup" is not a real lockup, Because many CPU try to get cache_disable_lock spin lock at the same time when kernel boot. And competition has occurred here. Every CPU's TLB will be flushed in the critical zone, the flushing TLB is a time-consuming operation, and there are so many CPUs, so the false "hard lockup" was detected by kernel. To avoid customer confuse, when Canonical do the fix? HW Config: ThinkSystem SR950 V3 CPU: 8* Intel(R) Xeon(R) Platinum 8490H 60 Core 3.5GHz MEM: 2TB = SK Hynix 356GB DDR5 4800MHz 3DS (2015.1GB) Raid: ThinkSystem RAID 940-8i 4GB Flash PCIe Gen4 12Gb Adapter Storage: Micron_7450_MTFDKBA960TFR *1 Samsung 30.7TB 24Gbps SAS 2.5" SSD NIC: ThinkSystem Intel X710-T4L 10GBASE-T 4-Port OCP Ethernet Adapter OS: ubuntu 24.04 LTS( kernel 6.8.0-38-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
Still occurs with linux 6.8.0-51-generic -- 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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. Workaround: Unbind "usb" driver from the device manually before suspending. That can be done to work automatically by a special script in /lib/systemd/system-sleep. Unbinding has the side effect that a new sink is created on resume from suspend. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981487] Re: kernel BUG/Oops errors from modprobe while the DRBG has not yet initialized (focal/fips-updates)
This bug is awaiting verification that the linux-aws-
fips/6.8.0-1021.23+fips1 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-aws-fips' to
'verification-done-noble-linux-aws-fips'. If the problem still exists,
change the tag 'verification-needed-noble-linux-aws-fips' to
'verification-failed-noble-linux-aws-fips'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-aws-fips-v2
verification-needed-noble-linux-aws-fips
--
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/1981487
Title:
kernel BUG/Oops errors from modprobe while the DRBG has not yet
initialized (focal/fips-updates)
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Invalid
Status in linux source package in Focal:
Fix Released
Status in linux source package in Jammy:
Invalid
Bug description:
[Impact]
* The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
errors during boot with the FIPS OpenSSL library installed
(but those don't cause issues), when it runs modprobe with
request_module() when looking up crypto algorithms/modules.
* The modprobe command happens to call the OpenSSL library,
and the FIPS version of OpenSSL calls getrandom(),
and the FIPS kernel calls the DRBG for that,
BUT it's _not yet_ initialized that early during boot
when the kernel can run modprobe via request_module().
(e.g., IPv6 initialization time.)
* The issue impacts the kernels in fips-updates only, per:
"UBUNTU: SAUCE: random: Use Crypto API DRBG for urandom in FIPS mode"
which exists in Focal, but not in Xenial/Bionic/Jammy.
* The issue only happens with the crypto algorithms, even
if they're built-in (i.e., modprobe is not needed).
[Fix]
* Fall back to CRNG while the DRBG is not yet initialized.
(Marcelo Cerri confirmed it's OK per other discussions.)
* The fix doesn't change the list and details of algorithms
as in /proc/crypto (e.g., name, driver, module, priority)
by the time the DRBG is initialized / initramfs started,
so even though behavior changes, the net effect doesn't.
* (Note: it's not possible to just use an initcall level
earlier than rootfs_initcall() so modprobe isn't there,
because fips_drbg_init() must run _after_ module_init()
level so that crypto_rng_reset() works, even though its
required module is built-in too.
[Test Steps]
* Install the kernel and openssl from fips-updates,
boot with fips=1, check dmesg for BUG/Oops errors:
$ sudo apt install linux-image-fips libssl1.1 # fips-updates
$ sudo vim /etc/default/grub # append fips=1 boot option
$ sudo update-grub && sudo reboot
$ sudo dmesg | grep BUG:
* Check/store the /proc/crypto file for comparisons.
You can boot with break=top as well, to check that
as early as possible, and copy into /run/initramfs/
then exit, to get it later in the rootfs.
[Regression Potential]
* The fix falls back to the regular CRNG for a while
in early boot. The CRNG is used permanently in the
non-FIPS kernels (and in FIPS kernels w/out fips=1),
so the code path is exercised/tested frequently.
* Regressions would most likely occur in calls to
getrandom() before the DRBG is initialized, but
that currently hits a BUG/Oops anyway.
[Original Bug Description]
$ sudo apt install --yes linux-image-fips # fips-updates
$ sudo vim /etc/default/grub # fips=1
$ sudo update-grub && sudo reboot
$ uname -r
5.4.0-1056-fips
$ cat /proc/cmdline
... fips=1
No errors with the original/non-FIPS openssl, because it does NOT call
getrandom():
$ dmesg | grep -c BUG:
0
$ dpkg -s libssl1.1 | grep ^Version:
Version: 1.1.1f-1ubuntu2.15
$ strace -e getrandom modprobe --version
kmod version 27
+ZSTD +XZ -ZLIB +LIBCRYPTO -EXPERIMENTAL
+++ exited with 0 +++
But if you install the FIPS openssl, it calls getrandom(), then
BUG/Oops happen:
$ sudo apt install libssl1.1 # updates initramfs
$ dpkg -s libssl1.1 | grep ^Version:
Version: 1.1.1f-1ubuntu2.fips.13.1
$ strace -e getrandom modprobe --version
getrandom("\xc4\x84\x26\x25\x6f\xd4\xed\x38\xdf\xa9\x67\xee\x15\x1c\xe3\x98",
16, GRND_NONBLOCK) = 16
getrandom("\xa1\xd6\x67\x3e\xe4\x90\xb3\x8b\xdf\xe6\x34\x2a\xa7\x50\xbc\x2f",
16, GRND_NONBLOCK) = 16
getrandom("\xf1\x3e\xe4\x27\x9d\x47\x8c\x4b\x8a\x39\x8c\xe1\x2e\xee\xfa\x45",
16, GRND_NONBLOCK) = 16
getrandom("\xfb\x34\x18\x44\xd8\x23\x4c\x87\x13\x2e
[Kernel-packages] [Bug 2093957] [NEW] Enable Coresight in Perf
Public bug reported: Many ARM servers relying on Coresight feature to tracing CPU events. Enable Coresight on Perf to ensure the coresight function works as expected on Ubuntu. Enabling Coresight will build/put the coresight feature/scripts within perf and perf will detect if CPU supports coresight if users launch any coresight feature. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2093957 Title: Enable Coresight in Perf Status in linux-nvidia package in Ubuntu: New Bug description: Many ARM servers relying on Coresight feature to tracing CPU events. Enable Coresight on Perf to ensure the coresight function works as expected on Ubuntu. Enabling Coresight will build/put the coresight feature/scripts within perf and perf will detect if CPU supports coresight if users launch any coresight feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2093957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062951] Re: Random flickering with Intel i915 (Gen4+ GPUs) on Linux
I also experience flickering/glitches with my Intel i7-10700k. ``` $ lspci -nnk | grep -A3 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) DeviceName: Onboard - Video Subsystem: ASUSTeK Computer Inc. CometLake-S GT2 [UHD Graphics 630] [1043:8694] Kernel driver in use: i915 ``` In my case I often see a glitchy horizontal line about a quarter of the way down from the top of the monitor screen. It is most prevalent when I use the mouse to drag a window through this region. This system was upgraded through successive Kubuntu LTS versions until finally arriving at Kubuntu 24.04.1. I tried the various changes to /etc/default/grub including `intel_iommu=igfx_off` and the flickering remained. Interestingly if I boot from a USB flash drive with the kubuntu-24.04.1-desktop-amd64.iso image then I do not experience any flickering. Following are some differences in packages that I noticed that may or may not be relevant to the problem. Output from `uname -a` on USB flash drive (upper) and on (lower) Linux kubuntu 6.8.0-41-generic #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 2 20:41:06 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux Linux kaby 6.8.0-51-generic #52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 5 13:09:44 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux Output from ` dpkg -l | grep -i intel | grep -vi intelligent` - on USB flash drive (no flickering) -- ``` ii firmware-sof-signed 2023.12.1-1ubuntu1 all Intel SOF firmware - signed ii i965-va-driver:amd64 2.4.1+dfsg1-1build2 amd64VAAPI driver for Intel G45 & HD Graphics family ii intel-media-va-driver:amd64 24.1.0+dfsg1-1 amd64VAAPI driver for the Intel GEN8+ Graphics family ii intel-microcode 3.20240813.0ubuntu0.24.04.2 amd64Processor microcode firmware for Intel CPUs ii iucode-tool 2.3.1-3build1 amd64Intel processor microcode tool ii libdrm-intel1:amd64 2.4.120-2build1 amd64Userspace interface to intel-specific kernel DRM services -- runtime ii libigdgmm12:amd6422.3.17+ds1-1 amd64Intel Graphics Memory Management Library -- shared library ii libipt2 2.0.6-1build1 amd64Intel Processor Trace Decoder Library ii xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 amd64X.Org X server -- Intel i8xx, i9xx display driver ``` on SSD (yes flickering) --- ``` ii firmware-sof-signed 2023.12.1-1ubuntu1.3all Intel SOF firmware - signed ii i965-va-driver:amd64 2.4.1+dfsg1-1build2 amd64VAAPI driver for Intel G45 & HD Graphics family ii i965-va-driver:i386 2.4.1+dfsg1-1build2 i386 VAAPI driver for Intel G45 & HD Graphics family ii intel-media-va-driver:amd64 24.1.0+dfsg1-1 amd64VAAPI driver for the Intel GEN8+ Graphics family ii intel-media-va-driver:i386 24.1.0+dfsg1-1 i386 VAAPI driver for the Intel GEN8+ Graphics family ii intel-microcode 3.20241112.0ubuntu0.24.04.1 amd64Processor microcode firmware for Intel CPUs ii iucode-tool 2.3.1-3build1 amd64Intel processor microcode tool ii libdrm-intel1:amd64 2.4.120-2build1 amd64Userspace interface to intel-specific kernel DRM services -- runtime ii libdrm-intel1:i386 2.4.120-2build1 i386 Userspace interface to intel-specific kernel DRM services -- runtime ii libigdgmm12:amd6422.3.17+ds1-1 amd64Intel Graphics Memory Management Library -- shared library ii libigdgmm12:i386 22.3.17+ds1-1 i386 Intel Graphics Memor
[Kernel-packages] [Bug 2091753] Re: Plymouth fails with kernel 6.8.0-50
I can confirm that workaround with a small change for AMD integrated graphics. Instead of "i915", I added "amdgpu" to /etc/initramfs- tools/modules and do the respective commands. Thanks @rfaull for figuring this out! -- 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/2091753 Title: Plymouth fails with kernel 6.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: Plymouth fails to fully boot with this kernel when asking for encryption password for local partition. The system freezes and can be recovered in rescue mode. Previous kernels accepted the password and continued to X as expected. Remove 'splash' from GRUB_CMDLINE_LINUX_DEFAULT="quiet" prevents plymouth from loading and booting continues to X after password is entered in when booting pauses and asks for the password in the terminal. This behaviour is true on laptops running Linux Mint (Wilma) and Ubuntu KDE 24.04 with encrypted partitions. On devices without encrypted partitions 'quiet splash' is included on the kernel command line and booting proceeds as expected. Ubuntu 6.8.0-50.51-generic 6.8.12 Description: Linux Mint 22 Release: 22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2091753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981487] Re: kernel BUG/Oops errors from modprobe while the DRBG has not yet initialized (focal/fips-updates)
** Changed in: linux (Ubuntu Focal)
Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned)
--
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/1981487
Title:
kernel BUG/Oops errors from modprobe while the DRBG has not yet
initialized (focal/fips-updates)
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Invalid
Status in linux source package in Focal:
Fix Released
Status in linux source package in Jammy:
Invalid
Bug description:
[Impact]
* The Focal FIPS kernel in fips-updates hits kernel BUG/Oops
errors during boot with the FIPS OpenSSL library installed
(but those don't cause issues), when it runs modprobe with
request_module() when looking up crypto algorithms/modules.
* The modprobe command happens to call the OpenSSL library,
and the FIPS version of OpenSSL calls getrandom(),
and the FIPS kernel calls the DRBG for that,
BUT it's _not yet_ initialized that early during boot
when the kernel can run modprobe via request_module().
(e.g., IPv6 initialization time.)
* The issue impacts the kernels in fips-updates only, per:
"UBUNTU: SAUCE: random: Use Crypto API DRBG for urandom in FIPS mode"
which exists in Focal, but not in Xenial/Bionic/Jammy.
* The issue only happens with the crypto algorithms, even
if they're built-in (i.e., modprobe is not needed).
[Fix]
* Fall back to CRNG while the DRBG is not yet initialized.
(Marcelo Cerri confirmed it's OK per other discussions.)
* The fix doesn't change the list and details of algorithms
as in /proc/crypto (e.g., name, driver, module, priority)
by the time the DRBG is initialized / initramfs started,
so even though behavior changes, the net effect doesn't.
* (Note: it's not possible to just use an initcall level
earlier than rootfs_initcall() so modprobe isn't there,
because fips_drbg_init() must run _after_ module_init()
level so that crypto_rng_reset() works, even though its
required module is built-in too.
[Test Steps]
* Install the kernel and openssl from fips-updates,
boot with fips=1, check dmesg for BUG/Oops errors:
$ sudo apt install linux-image-fips libssl1.1 # fips-updates
$ sudo vim /etc/default/grub # append fips=1 boot option
$ sudo update-grub && sudo reboot
$ sudo dmesg | grep BUG:
* Check/store the /proc/crypto file for comparisons.
You can boot with break=top as well, to check that
as early as possible, and copy into /run/initramfs/
then exit, to get it later in the rootfs.
[Regression Potential]
* The fix falls back to the regular CRNG for a while
in early boot. The CRNG is used permanently in the
non-FIPS kernels (and in FIPS kernels w/out fips=1),
so the code path is exercised/tested frequently.
* Regressions would most likely occur in calls to
getrandom() before the DRBG is initialized, but
that currently hits a BUG/Oops anyway.
[Original Bug Description]
$ sudo apt install --yes linux-image-fips # fips-updates
$ sudo vim /etc/default/grub # fips=1
$ sudo update-grub && sudo reboot
$ uname -r
5.4.0-1056-fips
$ cat /proc/cmdline
... fips=1
No errors with the original/non-FIPS openssl, because it does NOT call
getrandom():
$ dmesg | grep -c BUG:
0
$ dpkg -s libssl1.1 | grep ^Version:
Version: 1.1.1f-1ubuntu2.15
$ strace -e getrandom modprobe --version
kmod version 27
+ZSTD +XZ -ZLIB +LIBCRYPTO -EXPERIMENTAL
+++ exited with 0 +++
But if you install the FIPS openssl, it calls getrandom(), then
BUG/Oops happen:
$ sudo apt install libssl1.1 # updates initramfs
$ dpkg -s libssl1.1 | grep ^Version:
Version: 1.1.1f-1ubuntu2.fips.13.1
$ strace -e getrandom modprobe --version
getrandom("\xc4\x84\x26\x25\x6f\xd4\xed\x38\xdf\xa9\x67\xee\x15\x1c\xe3\x98",
16, GRND_NONBLOCK) = 16
getrandom("\xa1\xd6\x67\x3e\xe4\x90\xb3\x8b\xdf\xe6\x34\x2a\xa7\x50\xbc\x2f",
16, GRND_NONBLOCK) = 16
getrandom("\xf1\x3e\xe4\x27\x9d\x47\x8c\x4b\x8a\x39\x8c\xe1\x2e\xee\xfa\x45",
16, GRND_NONBLOCK) = 16
getrandom("\xfb\x34\x18\x44\xd8\x23\x4c\x87\x13\x2e\x6b\x03\x79\xa7\x99\xf8",
16, 0) = 16
getrandom("\xdd\x83\xa7\x02\x10\x51\x2b\x4f\x21\x6b\xc1\xf1\x0d\xe7\x44\xb7",
16, 0) = 16
kmod version 27
+ZSTD +XZ -ZLIB +LIBCRYPTO -EXPERIMENTAL
+++ exited with 0 +++
$ sudo reboot
$ dmesg | grep -c BUG:
22
$ dmesg
...
[1.595759] NET: Registered protocol family 10
[1.600256] BUG: kernel NULL pointer dereference, address: 0038
...
[1.603829] CPU: 2 PID: 137 Comm: modprobe Not tainted 5.4.0-1056-fips
#64-Ubuntu
[1.603829] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
1.13.0-1ubuntu1.1 04/01/2014
[1.603829] RIP: 0010:urandom_read+0x268/0x480
...
[1.603829]
[Kernel-packages] [Bug 2093871] [NEW] Using sendpages_ok() in nvme_tcp_try_send_data()
Public bug reported: Can you please cherry-pick those 2 important commits from upstream? 1. net: introduce helper sendpages_ok() (https://github.com/torvalds/linux/commit/23a55f44) Network drivers are using sendpage_ok() to check the first page of an iterator in order to disable MSG_SPLICE_PAGES. The iterator can represent list of contiguous pages. When MSG_SPLICE_PAGES is enabled skb_splice_from_iter() is being used, it requires all pages in the iterator to be sendable. Therefore it needs to check that each page is sendable. The patch introduces a helper sendpages_ok(), it returns true if all the contiguous pages are sendable. Drivers who want to send contiguous pages with MSG_SPLICE_PAGES may use this helper to check whether the page list is OK. If the helper does not return true, the driver should remove MSG_SPLICE_PAGES flag. 2. nvme-tcp: use sendpages_ok() instead of sendpage_ok() (https://github.com/torvalds/linux/commit/6af7331a) Currently nvme_tcp_try_send_data() use sendpage_ok() in order to disable MSG_SPLICE_PAGES, it check the first page of the iterator, the iterator may represent contiguous pages. MSG_SPLICE_PAGES enables skb_splice_from_iter() which checks all the pages it sends with sendpage_ok(). When nvme_tcp_try_send_data() sends an iterator that the first page is sendable, but one of the other pages isn't skb_splice_from_iter() warns and aborts the data transfer. Using the new helper sendpages_ok() in order to disable MSG_SPLICE_PAGES solves the issue. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/2093871 Title: Using sendpages_ok() in nvme_tcp_try_send_data() Status in linux package in Ubuntu: New Bug description: Can you please cherry-pick those 2 important commits from upstream? 1. net: introduce helper sendpages_ok() (https://github.com/torvalds/linux/commit/23a55f44) Network drivers are using sendpage_ok() to check the first page of an iterator in order to disable MSG_SPLICE_PAGES. The iterator can represent list of contiguous pages. When MSG_SPLICE_PAGES is enabled skb_splice_from_iter() is being used, it requires all pages in the iterator to be sendable. Therefore it needs to check that each page is sendable. The patch introduces a helper sendpages_ok(), it returns true if all the contiguous pages are sendable. Drivers who want to send contiguous pages with MSG_SPLICE_PAGES may use this helper to check whether the page list is OK. If the helper does not return true, the driver should remove MSG_SPLICE_PAGES flag. 2. nvme-tcp: use sendpages_ok() instead of sendpage_ok() (https://github.com/torvalds/linux/commit/6af7331a) Currently nvme_tcp_try_send_data() use sendpage_ok() in order to disable MSG_SPLICE_PAGES, it check the first page of the iterator, the iterator may represent contiguous pages. MSG_SPLICE_PAGES enables skb_splice_from_iter() which checks all the pages it sends with sendpage_ok(). When nvme_tcp_try_send_data() sends an iterator that the first page is sendable, but one of the other pages isn't skb_splice_from_iter() warns and aborts the data transfer. Using the new helper sendpages_ok() in order to disable MSG_SPLICE_PAGES solves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2093871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2089306] Re: vfio_pci soft lockup on VM start while using PCIe passthrough
chrisyin233,
The reverts here will be included in the -generic kernels, they have
been applied to the Noble and Oracular trees as of today.
They are not included in 6.8.0-52.53-generic, as this version is from
the s2024.12.02 security cycle. They are slated to be included in the
2025.01.13 cycle release.
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Oracular)
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/2089306
Title:
vfio_pci soft lockup on VM start while using PCIe passthrough
Status in linux package in Ubuntu:
Invalid
Status in linux-nvidia package in Ubuntu:
Invalid
Status in linux-nvidia-6.11 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Committed
Status in linux-nvidia source package in Noble:
Fix Released
Status in linux-nvidia-6.11 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Fix Committed
Bug description:
When starting a VM with a passthrough PCIe device, the vfio_pci driver
will block while its fault handler pre-faults the entire mapped area.
For PCIe devices with large BAR regions this takes a very long time to
complete, and thus causes soft lockup warnings on the host. This
process can take hours with multiple passthrough large BAR region PCIe
devices.
This issue was introduced in kernel version 6.8.0-48-generic, with the
addition of patches "vfio/pci: Use unmap_mapping_range()" and
"vfio/pci: Insert full vma on mmap'd MMIO fault".
The patch "vfio/pci: Use unmap_mapping_range()" rewrote the way VFIO
tracks mapped regions to use the "vmf_insert_pfn" function instead of
tracking them itself and using "io_remap_pfn_range". The
implementation using "vmf_insert_pfn" is significantly slower.
The patch "vfio/pci: Insert full vma on mmap'd MMIO fault" introduced
this pre-faulting behavior, causing soft lockup warnings on the host
while the VM launches.
Without "vfio/pci: Insert full vma on mmap'd MMIO fault", a guest OS
experiences significantly longer boot times as faults are generated
while configuring the passthrough PCIe devices, but the host does not
see soft lockup warnings.
Both of these performance issues are resolved upstream by patchset
[1], but this would be a complex backport to 6.8, with significant
changes to core parts of the kernel.
The "vfio/pci: Use unmap_mapping_range()" patch was introduced as part
of patchset [2], and is intended to resolve a WARN_ON splat introduced
by the upstream patch ba168b52bf8e ("mm: use rwsem assertion macros
for mmap_lock"). However, this mmap_lock patch is not present in
noble:linux, and hence noble:linux was never impacted by the WARN_ON
issue.
Thus, we can safely revert the following patches to resolve this VFIO
slowdown:
- "vfio/pci: Insert full vma on mmap'd MMIO fault"
- "vfio/pci: Use unmap_mapping_range()"
[1] https://patchwork.kernel.org/project/linux-mm/list/?series=883517
[2]
https://lore.kernel.org/all/20240530045236.1005864-3-alex.william...@redhat.com/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089306/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2093077] Re: Fix Mic Mute LED not working problem on Dell Tarako platform
Hello Chris, or anyone else affected, Accepted firmware-sof into oracular-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/firmware- sof/2024.06-1ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- oracular to verification-done-oracular. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-oracular. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: firmware-sof (Ubuntu Oracular) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-oracular ** Changed in: firmware-sof (Ubuntu Noble) Status: New => Fix Committed ** Tags added: verification-needed-noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2093077 Title: Fix Mic Mute LED not working problem on Dell Tarako platform Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in firmware-sof source package in Noble: Fix Committed Status in firmware-sof source package in Oracular: Fix Committed Status in firmware-sof source package in Plucky: Fix Released Bug description: [SRU Justifications] == firmware-sof == [Impact] The mic-mute led not working on Dell Tarako laptops with Cirrus Audio Codec. [Fix] For firmware-sof, it required the updated sof-rpl-cs42l43-l0.tplg to remove the useless 'PGA5.0 5 Master Capture Switch' and 'PGA2.0 2 Master Capture Switch' for Mic Mute LED control [Test Case] 1. install firmware-sof-signed with version >= 2023.12.1-1ubuntu1.4. 2. press mic-mute hot-key and check if mic-mute LED is toggled correctly and aligned with the Mic-Mute status. [Where problems could occur] The topology only affects the particular Intel platforms with configuration which connects the cs42l43 codec on link #0 of soundwire. Should be low risk for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2093077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2093077] Please test proposed package
Hello Chris, or anyone else affected, Accepted firmware-sof into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/firmware- sof/2023.12.1-1ubuntu1.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- noble to verification-done-noble. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-noble. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to firmware-sof in Ubuntu. https://bugs.launchpad.net/bugs/2093077 Title: Fix Mic Mute LED not working problem on Dell Tarako platform Status in HWE Next: New Status in firmware-sof package in Ubuntu: Fix Released Status in firmware-sof source package in Noble: Fix Committed Status in firmware-sof source package in Oracular: Fix Committed Status in firmware-sof source package in Plucky: Fix Released Bug description: [SRU Justifications] == firmware-sof == [Impact] The mic-mute led not working on Dell Tarako laptops with Cirrus Audio Codec. [Fix] For firmware-sof, it required the updated sof-rpl-cs42l43-l0.tplg to remove the useless 'PGA5.0 5 Master Capture Switch' and 'PGA2.0 2 Master Capture Switch' for Mic Mute LED control [Test Case] 1. install firmware-sof-signed with version >= 2023.12.1-1ubuntu1.4. 2. press mic-mute hot-key and check if mic-mute LED is toggled correctly and aligned with the Mic-Mute status. [Where problems could occur] The topology only affects the particular Intel platforms with configuration which connects the cs42l43 codec on link #0 of soundwire. Should be low risk for regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2093077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061373] Re: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta
** Changed in: linux (Ubuntu) Assignee: Kleber Sacilotto de Souza (kleber-souza) => Manuel Diewald (diewald) ** Changed in: linux (Ubuntu Noble) Assignee: Kleber Sacilotto de Souza (kleber-souza) => Manuel Diewald (diewald) -- 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/2061373 Title: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta Status in grub2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in grub2 source package in Noble: Invalid Status in linux source package in Noble: Triaged Bug description: 1.The Version of product # lsb_release -rd No LSB modules are available. Description:Ubuntu Noble Numbat (development branch) Release:24.04 2.The version of package root@t:/tmp# apt-cache policy linux-image-6.8.0-22-generic linux-image-6.8.0-22-generic: Installed: 6.8.0-22.22 Candidate: 6.8.0-22.22 Version table: *** 6.8.0-22.22 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status 3.Expected to happen Print kernel output information after the server's POST screen disappears 4.Actual happend Print kernel output information before the server's POST screen disappears Please refer to the attached screenshot for details ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 15 07:46 seq crw-rw 1 root audio 116, 33 Apr 15 07:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Mon Apr 15 08:26:52 2024 InstallationDate: Installed on 2024-04-15 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Lenovo ThinkSystem SR650 V3 MB,EGS,DDR5,SH,2U PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=77cf1cbe-6d2e-4dec-9439-c7aa2a69b5d9 ro RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2023 dmi.bios.release: 3.10 dmi.bios.vendor: Lenovo dmi.bios.version: ESE121R-3.10 dmi.board.asset.tag: None dmi.board.name: STA7B05327 dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: None dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.ec.firmware.release: 3.90 dmi.modalias: dmi:bvnLenovo:bvrESE121R-3.10:bd11/15/2023:br3.10:efr3.90:svnLenovo:pnThinkSystemSR650V3MB,EGS,DDR5,SH,2U:pvr05:rvnLenovo:rnSTA7B05327:rvr05:cvnLenovo:ct23:cvrNone:sku7D75CTO0WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V3 MB,EGS,DDR5,SH,2U dmi.product.sku: 7D75CTO0WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2061373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2093871] Re: Using sendpages_ok() in nvme_tcp_try_send_data()
To use sendpages_ok() in nvme_tcp_try_send_data(), check if the data can be sent as memory pages for efficient transmission. If sendpages_ok() returns true, send the data using sendpages(). If it returns false, use alternative methods like sendmsg() to send the data in smaller chunks. This approach improves performance, especially when transferring large amounts of data over NVMe/TCP. -- 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/2093871 Title: Using sendpages_ok() in nvme_tcp_try_send_data() Status in linux package in Ubuntu: New Bug description: Can you please cherry-pick those 2 important commits from upstream? 1. net: introduce helper sendpages_ok() (https://github.com/torvalds/linux/commit/23a55f44) Network drivers are using sendpage_ok() to check the first page of an iterator in order to disable MSG_SPLICE_PAGES. The iterator can represent list of contiguous pages. When MSG_SPLICE_PAGES is enabled skb_splice_from_iter() is being used, it requires all pages in the iterator to be sendable. Therefore it needs to check that each page is sendable. The patch introduces a helper sendpages_ok(), it returns true if all the contiguous pages are sendable. Drivers who want to send contiguous pages with MSG_SPLICE_PAGES may use this helper to check whether the page list is OK. If the helper does not return true, the driver should remove MSG_SPLICE_PAGES flag. 2. nvme-tcp: use sendpages_ok() instead of sendpage_ok() (https://github.com/torvalds/linux/commit/6af7331a) Currently nvme_tcp_try_send_data() use sendpage_ok() in order to disable MSG_SPLICE_PAGES, it check the first page of the iterator, the iterator may represent contiguous pages. MSG_SPLICE_PAGES enables skb_splice_from_iter() which checks all the pages it sends with sendpage_ok(). When nvme_tcp_try_send_data() sends an iterator that the first page is sendable, but one of the other pages isn't skb_splice_from_iter() warns and aborts the data transfer. Using the new helper sendpages_ok() in order to disable MSG_SPLICE_PAGES solves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2093871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2094656] [NEW] dmsg stack trace because zfs_log.c bug => upgrade to 2.2.7
Public bug reported: As explained here: https://github.com/openzfs/zfs/issues/16621 I still run into this bug. This has been fixed with zfs-2.2.7 over a month ago. So while this is not as severe as the zfs file system corruption bug that was in 2.2.0, having a ZFS stack traces in the system log is not something you wanna see on a daily use system. So please update the packages for 24.10 to upstream zfs-2.2.7. Since ZFS is a critical part of the OS I really would appreciate if there would be a closer issue tracking and package update handling done by Ubuntu. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Description changed: As explained here: https://github.com/openzfs/zfs/issues/16621 I still run into this bug. This has been fixed with zfs-2.2.7 over a month ago. - So while this is not as severe as the zfs filesystem coruption bug that was in 2.2.0, + So while this is not as severe as the zfs file system corruption bug that was in 2.2.0, have ZFS stack traces in the system log is not something you wanna see on a daily use system. So please update the packages for 24.10 to upstream zfs-2.2.7. Since ZFS is a critical part of the OS I really would appreciate if there would be a closer issue tracking and package update handling done by Ubuntu. ** Description changed: As explained here: https://github.com/openzfs/zfs/issues/16621 I still run into this bug. This has been fixed with zfs-2.2.7 over a month ago. So while this is not as severe as the zfs file system corruption bug that was in 2.2.0, - have ZFS stack traces in the system log is not something you wanna see on a daily use system. + having a ZFS stack traces in the system log is not something you wanna see on a daily use system. So please update the packages for 24.10 to upstream zfs-2.2.7. Since ZFS is a critical part of the OS I really would appreciate if there would be a closer issue tracking and package update handling done by Ubuntu. -- 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/2094656 Title: dmsg stack trace because zfs_log.c bug => upgrade to 2.2.7 Status in zfs-linux package in Ubuntu: New Bug description: As explained here: https://github.com/openzfs/zfs/issues/16621 I still run into this bug. This has been fixed with zfs-2.2.7 over a month ago. So while this is not as severe as the zfs file system corruption bug that was in 2.2.0, having a ZFS stack traces in the system log is not something you wanna see on a daily use system. So please update the packages for 24.10 to upstream zfs-2.2.7. Since ZFS is a critical part of the OS I really would appreciate if there would be a closer issue tracking and package update handling done by Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2094656/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2082060] Re: memcpy: detected field-spanning write (size 8) of single field "lr + 1"
2.2.7 and 2.3.0 have been released. Time to backport? -- 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 write (size 8) of single field "lr + 1" Status in zfs-linux package in Ubuntu: Confirmed Bug description: I upgraded one of my systems to Oracular and noticed this error: memcpy: detected field-spanning write (size 8) of single field "lr + 1" at /build/linux-3RcvoW/linux-6.11.0/debian/build/build- generic/dkms/build/zfs/2.2.6/build/module/zfs/zfs_log.c:461 (size 0) I'm running kernel 6.11.0-8-generic and zfs 2.2.6-1ubuntu1 See also: memcpy: detected field-spanning write #16501 - https://github.com/openzfs/zfs/issues/16501 memcpy: detected field-spanning write (size 7) of single field "sbuf" at /var/lib/dkms/zfs/2.2.99/build/module/lua/lstring.c:107 - https://github.com/openzfs/zfs/issues/16541 --- ProblemType: Bug ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:danilo 3545 F pipewire /dev/snd/controlC0: danilo 3550 F wireplumber CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.10 InstallationDate: Installed on 2024-09-11 (15 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 04f2:b47f Chicony Electronics Co., Ltd VGA Webcam Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 005: ID 04ca:3014 Lite-On Technology Corp. Qualcomm Atheros Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Acer Aspire ES1-572 NonfreeKernelModules: zfs Package: linux (not installed) ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=screen-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x44vyn@/vmlinuz-6.11.0-8-generic root=ZFS=rpool/ROOT/ubuntu_x44vyn ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=1 ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0 RelatedPackageVersions: linux-restricted-modules-6.11.0-8-generic N/A linux-backports-modules-6.11.0-8-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 Tags: oracular Uname: Linux 6.11.0-8-generic x86_64 UnreportableReason: Este relatório é sobre o pacote que não foi instalado. UpgradeStatus: Upgraded to oracular on 2024-09-25 (1 days ago) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 06/20/2016 dmi.bios.release: 1.2 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: T-Rex_SK dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd06/20/2016:br1.2:efr1.2:svnAcer:pnAspireES1-572:pvrV1.02:rvnAcer:rnT-Rex_SK:rvrV1.02:cvnAcer:ct10:cvrV1.02:skuAspireES1-572_1085_V1.02: dmi.product.family: SKL dmi.product.name: Aspire ES1-572 dmi.product.sku: Aspire ES1-572_1085_V1.02 dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2082060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2093871] Re: Using sendpages_ok() in nvme_tcp_try_send_data()
Does it fix any 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/2093871 Title: Using sendpages_ok() in nvme_tcp_try_send_data() Status in linux package in Ubuntu: New Bug description: Can you please cherry-pick those 2 important commits from upstream? 1. net: introduce helper sendpages_ok() (https://github.com/torvalds/linux/commit/23a55f44) Network drivers are using sendpage_ok() to check the first page of an iterator in order to disable MSG_SPLICE_PAGES. The iterator can represent list of contiguous pages. When MSG_SPLICE_PAGES is enabled skb_splice_from_iter() is being used, it requires all pages in the iterator to be sendable. Therefore it needs to check that each page is sendable. The patch introduces a helper sendpages_ok(), it returns true if all the contiguous pages are sendable. Drivers who want to send contiguous pages with MSG_SPLICE_PAGES may use this helper to check whether the page list is OK. If the helper does not return true, the driver should remove MSG_SPLICE_PAGES flag. 2. nvme-tcp: use sendpages_ok() instead of sendpage_ok() (https://github.com/torvalds/linux/commit/6af7331a) Currently nvme_tcp_try_send_data() use sendpage_ok() in order to disable MSG_SPLICE_PAGES, it check the first page of the iterator, the iterator may represent contiguous pages. MSG_SPLICE_PAGES enables skb_splice_from_iter() which checks all the pages it sends with sendpage_ok(). When nvme_tcp_try_send_data() sends an iterator that the first page is sendable, but one of the other pages isn't skb_splice_from_iter() warns and aborts the data transfer. Using the new helper sendpages_ok() in order to disable MSG_SPLICE_PAGES solves the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2093871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2094048] [NEW] Pick up patches that were missed in the work to create a new linux-nvidia-6.11 kernel
Public bug reported: a number of patches were not carried forward. The following collection of patches should be cherry-picked: Commit Summary 6adf616 cppc_cpufreq: Use desired perf if feedback ctrs are 0 or unchanged cd955fc cppc_cpufreq: Remove HiSilicon CPPC workaround ae2224f NVIDIA: SAUCE: ACPI/HMAT: Move HMAT messages to pr_debug() 404b06a perf cs-etm: Create decoders after both AUX and HW_ID search passes 6dc551f perf: cs-etm: Allocate queues for all CPUs 0695b8e perf: cs-etm: Move traceid_list to each queue 4cb2195 perf: cs-etm: Create decoders based on the trace ID mappings 7abe526 perf: cs-etm: Only save valid trace IDs into files 6a74057 perf: cs-etm: Support version 0.1 of HW_ID packets a82a4c6 perf: cs-etm: Print queue number in raw trace dump f1fbb5b coresight: Remove unused ETM Perf stubs aefc384 coresight: Clarify comments around the PID of the sink owner 1676c55 coresight: Move struct coresight_trace_id_map to common header 975a565 coresight: Expose map arguments in trace ID API 11b2f11 coresight: Make CPU id map a property of a trace ID map 6455295 coresight: Use per-sink trace ID maps for Perf sessions f273c8e coresight: Remove pending trace ID release mechanism 09e8442 coresight: Emit sink ID in the HW_ID packets 9418582 coresight: Make trace ID map spinlock local to the map ** Affects: linux-nvidia-6.11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.11 in Ubuntu. https://bugs.launchpad.net/bugs/2094048 Title: Pick up patches that were missed in the work to create a new linux- nvidia-6.11 kernel Status in linux-nvidia-6.11 package in Ubuntu: New Bug description: a number of patches were not carried forward. The following collection of patches should be cherry-picked: Commit Summary 6adf616 cppc_cpufreq: Use desired perf if feedback ctrs are 0 or unchanged cd955fc cppc_cpufreq: Remove HiSilicon CPPC workaround ae2224f NVIDIA: SAUCE: ACPI/HMAT: Move HMAT messages to pr_debug() 404b06a perf cs-etm: Create decoders after both AUX and HW_ID search passes 6dc551f perf: cs-etm: Allocate queues for all CPUs 0695b8e perf: cs-etm: Move traceid_list to each queue 4cb2195 perf: cs-etm: Create decoders based on the trace ID mappings 7abe526 perf: cs-etm: Only save valid trace IDs into files 6a74057 perf: cs-etm: Support version 0.1 of HW_ID packets a82a4c6 perf: cs-etm: Print queue number in raw trace dump f1fbb5b coresight: Remove unused ETM Perf stubs aefc384 coresight: Clarify comments around the PID of the sink owner 1676c55 coresight: Move struct coresight_trace_id_map to common header 975a565 coresight: Expose map arguments in trace ID API 11b2f11 coresight: Make CPU id map a property of a trace ID map 6455295 coresight: Use per-sink trace ID maps for Perf sessions f273c8e coresight: Remove pending trace ID release mechanism 09e8442 coresight: Emit sink ID in the HW_ID packets 9418582 coresight: Make trace ID map spinlock local to the map To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.11/+bug/2094048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061373] Re: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta
Hi Kelvin, thanks for confirming my suspicion. This bug affects noble (24.04 LTS), the jammy hwe kernel (22.04 LTS) and oracular (24.10). The earliest that we could land a fix for these affected series is in the upcoming SRU cycle that will release kernels (tentatively) in the first week of March. -- 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/2061373 Title: [Lenovo Ubuntu 24.04 Bug] Print grub message before the uefi POST screen disappears in Ubuntu24.04 Beta Status in grub2 package in Ubuntu: Invalid Status in linux package in Ubuntu: Triaged Status in grub2 source package in Noble: Invalid Status in linux source package in Noble: Triaged Bug description: 1.The Version of product # lsb_release -rd No LSB modules are available. Description:Ubuntu Noble Numbat (development branch) Release:24.04 2.The version of package root@t:/tmp# apt-cache policy linux-image-6.8.0-22-generic linux-image-6.8.0-22-generic: Installed: 6.8.0-22.22 Candidate: 6.8.0-22.22 Version table: *** 6.8.0-22.22 500 500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages 100 /var/lib/dpkg/status 3.Expected to happen Print kernel output information after the server's POST screen disappears 4.Actual happend Print kernel output information before the server's POST screen disappears Please refer to the attached screenshot for details ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-22-generic 6.8.0-22.22 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 15 07:46 seq crw-rw 1 root audio 116, 33 Apr 15 07:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass Date: Mon Apr 15 08:26:52 2024 InstallationDate: Installed on 2024-04-15 (0 days ago) InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.1) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Lenovo ThinkSystem SR650 V3 MB,EGS,DDR5,SH,2U PciMultimedia: ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm XDG_RUNTIME_DIR= ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=77cf1cbe-6d2e-4dec-9439-c7aa2a69b5d9 ro RelatedPackageVersions: linux-restricted-modules-6.8.0-22-generic N/A linux-backports-modules-6.8.0-22-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2023 dmi.bios.release: 3.10 dmi.bios.vendor: Lenovo dmi.bios.version: ESE121R-3.10 dmi.board.asset.tag: None dmi.board.name: STA7B05327 dmi.board.vendor: Lenovo dmi.board.version: 05 dmi.chassis.asset.tag: None dmi.chassis.type: 23 dmi.chassis.vendor: Lenovo dmi.chassis.version: None dmi.ec.firmware.release: 3.90 dmi.modalias: dmi:bvnLenovo:bvrESE121R-3.10:bd11/15/2023:br3.10:efr3.90:svnLenovo:pnThinkSystemSR650V3MB,EGS,DDR5,SH,2U:pvr05:rvnLenovo:rnSTA7B05327:rvr05:cvnLenovo:ct23:cvrNone:sku7D75CTO0WW: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem SR650 V3 MB,EGS,DDR5,SH,2U dmi.product.sku: 7D75CTO0WW dmi.product.version: 05 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/2061373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2084046] Re: [i915] Phantom "Unknown" display detected on Intel Meteor Lake
Hi Matthew,
I tested your noble-kernel and it does indeed fix the issue, thank you
very much!
--
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 Meteor Lake
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Fix Committed
Bug description:
Settings is reporting a second display ("Unknown") is connected. This
is on a laptop which has nothing plugged in and only an Intel GPU.
It appears the problem is once again (like bug 2060268) SimpleDRM:
Node: /dev/dri/card0
├───Driver: simpledrm (DRM driver for simple-framebuffer platform devices)
version 1.0.0 (0)
--
Node: /dev/dri/card1
├───Driver: i915 (Intel Graphics) version 1.6.0 (0)
Linux version 6.11.0-8-generic (buildd@lcy02-amd64-042) (x86_64-linux-
gnu-gcc-14 (Ubuntu 14.2.0-4ubuntu2) 14.2.0, GNU ld (GNU Binutils for
Ubuntu) 2.43.1) #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 13:41:20 UTC
2024 (Ubuntu 6.11.0-8.8-generic 6.11.0)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084046/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2094190] [NEW] 2024.10.07 new upstream release
Public bug reported: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to-date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda (<< k4.15) or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. ** Affects: wireless-regdb (Ubuntu) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Focal) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Noble) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Oracular) Importance: Undecided Status: New ** Affects: wireless-regdb (Ubuntu Plucky) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Plucky) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Oracular) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: wireless-regdb (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/2094190 Title: 2024.10.07 new upstream release Status in wireless-regdb package in Ubuntu: New Status in wireless-regdb source package in Trusty: New Status in wireless-regdb source package in Xenial: New Status in wireless-regdb source package in Bionic: New Status in wireless-regdb source package in Focal: New Status in wireless-regdb source package in Jammy: New Status in wireless-regdb source package in Noble: New Status in wireless-regdb source package in Oracular: New Status in wireless-regdb source package in Plucky: New Bug description: [Impact] New upstream release. This is a database of wireless regulations, and should updated in all releases to ensure users have the most up-to- date regulatory information. [Test Case] Following reboot after installing the new database, it should be possible to query and change the regulatory domain using 'iw reg get' and 'iw reg set'. [Where problems could occur] If crda (<< k4.15) or the kernel is unable to use the new database, users may be stuck using the default "world" regulatory domain which is quite restrictive, therefore they may be unable to use wireless channels that they were able to use previously. Regulatory rules may have also changed for the user's region, which could also make some channels unusable, but this would not be a bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/2094190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2084046] Re: [i915] Phantom "Unknown" display detected on Intel Meteor Lake
Hi Justus,
Thanks for testing. We now know the fix, which is great news.
We just need to get it out to everyone now.
I see the Kernel Team has just tagged 6.8.0-52-generic, but
"firmware/sysfb: Disable sysfb for firmware buffers with unknown parent"
isn't in there. It looks like it might be a part of the next SRU cycle
instead.
ubuntu-noble$ git log --grep "firmware/sysfb: Disable sysfb for firmware
buffers with unknown parent" origin/master-next
commit 4f3ddc70111bd257bf9fbdfe43cd58d9fb67d72c
Author: Thomas Zimmermann
Date: Tue Sep 24 10:41:03 2024 +0200
firmware/sysfb: Disable sysfb for firmware buffers with unknown parent
ubuntu-noble$ git describe --contains 4f3ddc70111bd257bf9fbdfe43cd58d9fb67d72c
fatal: cannot describe '4f3ddc70111bd257bf9fbdfe43cd58d9fb67d72c'
$ git log --grep "firmware/sysfb: Disable sysfb for firmware buffers with
unknown parent" Ubuntu-6.8.0-52.53
(nothing)
I'll see what I can do. Worst case, it will be approx 2 months away.
Thanks,
Matthew
--
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 Meteor Lake
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Fix Committed
Bug description:
Settings is reporting a second display ("Unknown") is connected. This
is on a laptop which has nothing plugged in and only an Intel GPU.
It appears the problem is once again (like bug 2060268) SimpleDRM:
Node: /dev/dri/card0
├───Driver: simpledrm (DRM driver for simple-framebuffer platform devices)
version 1.0.0 (0)
--
Node: /dev/dri/card1
├───Driver: i915 (Intel Graphics) version 1.6.0 (0)
Linux version 6.11.0-8-generic (buildd@lcy02-amd64-042) (x86_64-linux-
gnu-gcc-14 (Ubuntu 14.2.0-4ubuntu2) 14.2.0, GNU ld (GNU Binutils for
Ubuntu) 2.43.1) #8-Ubuntu SMP PREEMPT_DYNAMIC Mon Sep 16 13:41:20 UTC
2024 (Ubuntu 6.11.0-8.8-generic 6.11.0)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084046/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
