[Kernel-packages] [Bug 2081856] Re: Instalation Ubuntu 24.10 Nvidia not install
this has released now ** Package changed: linux (Ubuntu) => linux-restricted-modules (Ubuntu) ** Changed in: linux-restricted-modules (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/2081856 Title: Instalation Ubuntu 24.10 Nvidia not install Status in linux-restricted-modules package in Ubuntu: Fix Released Bug description: When I'm installing Ubuntu 24.10, when I get to the part where the system installs the Nvidia drivers, I think it's nvidia-560, it can't sign in to boot secure and the installation stops. It can't sign the secure boot and the installation doesn't proceed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2081856/+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 2081856] Re: Instalation Ubuntu 24.10 Nvidia not install
If it really does offer 560, then this will be fixed once the linux- restricted-modules update lands. It'll provide prebuilt and signed modules. ** Changed in: linux (Ubuntu) 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.launchpad.net/bugs/2081856 Title: Instalation Ubuntu 24.10 Nvidia not install Status in linux package in Ubuntu: In Progress Bug description: When I'm installing Ubuntu 24.10, when I get to the part where the system installs the Nvidia drivers, I think it's nvidia-560, it can't sign in to boot secure and the installation stops. It can't sign the secure boot and the installation doesn't proceed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081856/+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 2070329] Re: KOP L2 guest fails to boot with 1 core - SMT8 topology
** Changed in: linux (Ubuntu Oracular) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2070329 Title: KOP L2 guest fails to boot with 1 core - SMT8 topology Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Released Bug description: SRU Justification: [ Impact ] * On a P10 system with SMT-8 configured a level 2 guest (VM) fails to boot in case it only has one core assigned. [ Test Plan ] * Setup an IBM Power 10 system - that support up to SMT-8 and with firmware 1060, that offers support for KVM - using Ubuntu Server 24.04 for ppc64el. * Setup qemu/KVM on this system. * Configure a KVM guest (e.g. using virtinst or qemu-system-ppc64 directly) now with smt-8, but only one virtual CPU. * Try to boot this specific guest: qemu-system-ppc64 \ -drive file=rhel.qcow2,format=qcow2 \ -m 20G \ -smp 8,cores=1,threads=8 \ -cpu host \ -nographic \ -machine pseries,ic-mode=xics -accel kvm * It will fail to boot with a kernel that does not have the two patches in place. * Since this setup requires a special firmware level, the verification will be done by the IBM Power team. [ Where problems could occur ] * Primarily support for using DPDES (register) is required, since its needed for enabling usage of doorbells in L2 gusts. This is mainly done by adding DEFINEs, stubs and case. If the definitions are not correct or if the code executed by the new case (KVMPPC_GSID_DPDES) is done wrong, the guest state could be incorrect, harming the L2 guest doorbell. (DPDES is to provide the means for the hypervisor to save a [sub-]processor's Directed Privileged Doorbell exception state when the set of programs running on the [sub-]processor is swapped out or moved from one [sub-]processor to another.) * The missing Doorbell emulation got added by a 4 line if statement in powerpc/kvm/book3s_hv.c, which is relatively traceable. * The main issue I can think of is that kvmppc_set_dpdes is called with wrong arguments. * And kvmppc_set_dpdes will not work (at all) if the above DPDES support (and commit/patch) is missing. [ Other Info ] * Since (nested) KVM support is new on P10, this does not affect older Power generation (P9 is the only other hw generation that is supported by 24.04, but it only supports native virtualization). * Both patches are upstream accepted since v6.11(-rc1), hence will be in oracular and are also upstream tagged as stable updates. * Since the required firmware FW1060 is relatively new, we can assume that not many user ran into this issue yet. __ == Comment: #0 - SEETEENA THOUFEEK - 2024-06-25 01:24:11 == +++ This bug was initially created as a clone of Bug #205277 +++ ---Problem Description--- KOP L2 guest fails to boot with 1 core - SMT8 topology ---Additional Hardware Info--- na ---Debugger Data--- na ---Steps to Reproduce--- KOP L2 guest fails to boot when we set the CPU topology as 1 core - SMT 8 command line used to verify the issue: #!/bin/sh QEMU="/home/mgautam/qemu" qemu-system-ppc64 -s \ -drive file=/root/debian-12-nocloud-ppc64el.qcow2,format=qcow2 \ -m 20G \ -smp 8,cores=1,sockets=1,threads=8 \ -cpu host \ -nographic \ -machine pseries,ic-mode=xics -accel kvm \ -net nic,model=virtio \ -net user,host=10.0.2.10,hostfwd=tcp:127.0.0.1:10022-:22 NOTE: L2 boots fine when doorbells are turned off in L1 kernel As per the investigation so far, the doorbell exception is not getting fired inside L2 guest. At L1 level, if we set DPDES=1 in the GSB for L2, the guest never receives the doorbell and also it is never cleared from the GSB. We are discussing this behaviour with phyp team. The root cause of this issue is lack of DPDES support at L1. I've posted the fix upstream - https://lore.kernel.org/linuxppc- dev/20240522084949.123148-1-gau...@linux.ibm.com/T/#u The fix has been accepted upstream and will be backported for kernels >= 6.7 https://lore.kernel.org/linuxppc- dev/20240605113913.83715-1-gau...@linux.ibm.com/ ---Patches Installed--- na ---System Hang--- na ---uname output--- na Contact Information = na Machine Type = na Userspace rpm: na Userspace tool common name: na The userspace tool has the following bit modes: na Userspace tool obtained from project website: na *Additional Instructions for na: -Post a private note with access information to the machine that is currently in the debugger. -Attach ltrace
[Kernel-packages] [Bug 2070253] Re: KVM on PowerVM: L2 Guest-Aggressively entering CEDE results in low performance. Possible tuning opportunity.
** Changed in: linux (Ubuntu Oracular) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2070253 Title: KVM on PowerVM: L2 Guest-Aggressively entering CEDE results in low performance. Possible tuning opportunity. Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Released Bug description: KVM on PowerVM: L2 Guest-Aggressively entering CEDE results in low performance. Possible tuning opportunity. ---uname output--- Linux rhel86edb1 #1 SMP Sun Jan 21 11:45:44 EST 2024 ppc64le ppc64le ppc64le GNU/Linux ---Steps to Reproduce--- Example: run READ only Test using EDB-PGBENCH and DT7 workloads on 1. L1-Host 2. L2-Guest CEDE ON 3. L2-Guest CEDE OFF significant performance drop is observed in L2-Guest CEDE on vs L2-Guest CEDE off case. Note: Host and Guest configuration used performance experiments are listed below. Location of EDB-PGBENCH: #wget http://ci-http-results.aus.stglabs.ibm.com/perfTest/scripts/Bug_Scripts/pgbench_install.sh #chmod 777 pgbench_install.sh #./pgbench_install.sh -->> it will install EDB(pgbench) and run edb on target lpar. Location of DT7 workload: #wget http://ci-http-results.aus.stglabs.ibm.com/perfTest/scripts/Bug_Scripts/DT7-Install.sh #chmod 777 DT7-Install.sh #./DT7-Install.sh -->> It will install DT7. Sample Commands : Once installation was successful run below commands on target lpar. EDB-PGBENCH Commands : # su - enterprisedb # vi t1.tc -->> copy below lines to t1.tc file . ##t1.tc## runname=select SCALE=100 runtime=300 thread="40" smtlist="8" mode=select recreateinstance=yes recreateduringrun=yes warmup=no perf_stat=yes PGSQL=/usr/local/pgsql/bin #PGSQL=/usr/edb/as14/bin #PGPORT=5432 cores=5 ##t1.tc## #cp t1.tc tc/ #./auto-run-test.sh DT7 Commands : After installation of DT7 run below command : #cd /root #./DayTrader7_Run.sh -u 20 -l 900 -i 2 ## Machine Type: Power 10 LPAR (RHEL9.3) gcc : 11.4.1 Memory: 300GB Test type : pgbench-edb, DT7 ## KVM Host lscpu output : # lscpu Architecture:ppc64le Byte Order:Little Endian CPU(s): 96 On-line CPU(s) list: 0-39 Off-line CPU(s) list: 40-95 Model name: POWER10 (architected), altivec supported Model: 2.0 (pvr 0080 0200) Thread(s) per core:8 Core(s) per socket:5 Socket(s): 1 Physical sockets: 1 Physical chips:4 Physical cores/chip: 12 Virtualization features: Hypervisor vendor: pHyp Virtualization type: para Caches (sum of all): L1d: 320 KiB (10 instances) L1i: 480 KiB (10 instances) L2:10 MiB (10 instances) L3:40 MiB (10 instances) NUMA: NUMA node(s): 1 NUMA node2 CPU(s): 0-39 Vulnerabilities: Gather data sampling: Not affected Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Retbleed: Not affected Spec rstack overflow: Not affected Spec store bypass: Not affected Spectre v1:Vulnerable, ori31 speculation barrier enabled Spectre v2:Vulnerable Srbds: Not affected Tsx async abort: Not affected ## KVM on PowerVM setup: KVM (Kernel Virtual Machine) is a virtualization module for Linux that provides the ability of virtualization to Linux i.e. it allows the kernel to function as a hypervisor. We used P10 2S4U system for this experiment. Workloads: DT7 and PGBENCH in details: DT7 is an open source benchmark application emulating an online stock trading system. DT7 consist of 3 components 1) Jmeter 2) WAS (WebSphere Application Server) 3) DB2 DayTrader benchmark/application will be installed/deployed on WAS and this used DB2 as a backbone database. Jmeter generate the request and interact with the WAS. which would be kind of middle ware. PGBENCH : pgbench is a simple program for running benchmark tests on PostgreSQL. It runs the same sequence of SQL commands over and over, possibly in multiple concurrent database sessions, and then calculates the average transaction rate (transac
[Kernel-packages] [Bug 2060039] Re: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang
** Changed in: linux (Ubuntu Oracular) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2060039 Title: [Ubuntu-24.04] FADump with recommended crash size is making the L1 hang Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Released Bug description: SRU Justification: [Impact] * L1 host hangs when triggering FADump that results in crash [Fix] * 353d7a84c214f184d5a6b62acdec8b4424159b7c 353d7a84c214 "powerpc/64s/radix/kfence: map __kfence_pool at page granularity" [Test Case] * Have a Ubuntu Server 24.04 LTS installation on ppc64el. * Enable FADump with 1GB: fadump=on crashkernel=1024M * A kernel panic will happen when dump got triggered [Regression Potential] * There is a certain risk of a regression, but it is mapping only the memory allocated for KFENCE pool at page granularity, reducing memory consumption when KFENCE is used. * On top the commit is already upstream reviewed and accepted. * The modifications were done and tested by IBM. * The fadump feature is supported only on IBM POWER systems. [Other] * The fix/commit got upstream accepted with kernel v6.11-rc4, hence Oracular (with a planned kernel of 6.11) is not affected. ... Problem description : == Triggered FADump with the recommended crash. L1 host got hung. As per the public document https://wiki.ubuntu.com/ppc64el/Recommendations recommended crash kernel size is 1024M for the system. But with 1024M and 2048M, the L1 is getting hanged. with 4096, crash is generated and collected. root@ubuntu2404:~# uname -ar Linux ubuntu2404 6.8.0-11-generic #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 ppc64le ppc64le ppc64le GNU/Linux root@ubuntu2404:~# free -h totalusedfree shared buff/cache available Mem:48Gi 1.7Gi46Gi13Mi 687Mi 46Gi Swap: 8.0Gi 0B 8.0Gi root@ubuntu2404:~# cat /proc/cmdline BOOT_IMAGE=/vmlinux-6.8.0-11-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro fadump=on crashkernel=1024M root@ubuntu2404:~# dmesg | grep -i reser [0.00] fadump: Reserved 1024MB of memory at 0x004000 (System RAM: 51200MB) [0.00] fadump: Initialized 0x4000 bytes cma area at 1024MB from 0x4007 bytes of memory reserved for firmware-assisted dump [0.00] Memory: 49316672K/52428800K available (23616K kernel code, 4096K rwdata, 25536K rodata, 8832K init, 2487K bss, 2063552K reserved, 1048576K cma-reserved) [0.396408] ibmvscsi 3066: Client reserve enabled root@ubuntu2404:~# kdump-config show DUMP_MODE:fadump USE_KDUMP:1 KDUMP_COREDIR:/var/crash /var/lib/kdump/vmlinuz kdump initrd: /var/lib/kdump/initrd.img current state:ready to fadump IBM is looking to update the crash kernel reservations section of the wiki for Power. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2060039/+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 2072641] Re: [UBUNTU 22.04] KVM: s390: unhandled guest LPSWEY instruction
** Changed in: linux (Ubuntu Oracular) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2072641 Title: [UBUNTU 22.04] KVM: s390: unhandled guest LPSWEY instruction Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Released Bug description: Description: KVM: s390: unhandled guest LPSWEY instruction Symptom: guest kernel oops on LPSWEY instruction Problem: in rare cases like machine check injection with PSW disabled, all load PSW instructions are intercepted. LPSW and LPSWE are handled by KVM but not the new LPSWEY Solution: Provide an LPSWEY handler in KVM. Reproduction: hotplug a device while a CPU is disabled for machine checks, e.g. during early boot Upstream-ID: 4c6abb7f7b349f00c0f7ed5045bf67759c012892 Preventive:yes Reported: upstream Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2072641/+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 2073583] Re: [SRU][22.04.5]: mpi3mr driver update
** Changed in: linux (Ubuntu Oracular) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2073583 Title: [SRU][22.04.5]: mpi3mr driver update Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Won't Fix Status in linux source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Released Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). [Fix] - cf82b9e866b6 : mpi3mr: Driver version update - 1c342b0548e3 : mpi3mr: Prevent PCI writes from driver during PCI error recovery - 30bafe1774f0 : mpi3mr: Support PCI Error Recovery callback handlers - 78b506984ebe : mpi3mr: Add ioctl support for HDB - d8d08d1638ce : mpi3mr: Trigger support - fc941140: mpi3mr: HDB allocation and posting for hardware and firmware buffers [Test Plan] - Driver load/unload - ro and r1 creation and deletion - By using management command tested hdb - Use sg_reset -H - Resetting the controller in a loop. [Where problems could occur] [Other Info] noble https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2073583_mpi3mr_update oracular https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/oracular/+ref/lp_2073583_mpi3mr_update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073583/+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 2076147] Re: Add 'mm: hold PTL from the first PTE while reclaiming a large folio' to fix L2 Guest hang during LTP Test
** Changed in: linux (Ubuntu Oracular) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2076147 Title: Add 'mm: hold PTL from the first PTE while reclaiming a large folio' to fix L2 Guest hang during LTP Test Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Released Bug description: SRU Justification: [ Impact ] * KVM 2nd level guest (means KVM VM that runs nested on top of a Power 10 PowerVM hypervisor) hangs during LTP (Linux Test Projects) test suite. * It hangs with: "Back trace of paca->saved_r1 (0xc00c1bc8bb00) (possibly stale) @ new_slab" * Diagnosing the issues points this this fix/upstream-commit: [commit message, by Barry Song ] Within try_to_unmap_one(), page_vma_mapped_walk() races with other PTE modifications preceded by pte clear. While iterating over PTEs of a large folio, it only starts acquiring PTL from the first valid (present) PTE. PTE modifications can temporarily set PTEs to pte_none. Consequently, the initial PTEs of a large folio might be skipped in try_to_unmap_one(). For example, for an anon folio, if we skip PTE0, we may have PTE0 which is still present, while PTE1 ~ PTE(nr_pages - 1) are swap entries after try_to_unmap_one(). So folio will be still mapped, the folio fails to be reclaimed and is put back to LRU in this round. This also breaks up PTEs optimization such as CONT-PTE on this large folio and may lead to accident folio_split() afterwards. And since a part of PTEs are now swap entries, accessing those parts will introduce overhead - do_swap_page. Although the kernel can withstand all of the above issues, the situation still seems quite awkward and warrants making it more ideal. The same race also occurs with small folios, but they have only one PTE, thus, it won't be possible for them to be partially unmapped. This patch [see below] holds PTL from PTE0, allowing us to avoid reading PTE values that are in the process of being transformed. With stable PTE values, we can ensure that this large folio is either completely reclaimed or that all PTEs remain untouched in this round. A corner case is that if we hold PTL from PTE0 and most initial PTEs have been really unmapped before that, we may increase the duration of holding PTL. Thus we only apply this optimization to folios which are still entirely mapped (not in deferred_split list). [ Fix ] * 73bc32875ee9 73bc32875ee9b1881dd780308c6793fe463fe803 "mm: hold PTL from the first PTE while reclaiming a large folio" [ Test Plan ] * An IBM Power 10 system (where PowerVM is mandatory) running Ubuntu Server 24.04 (kernel 6.8) or later with (nested) KVM setup (so KVM on top of PowerVM). * Run LTP test suite Tests running: SLS(io,base) * Without the patch the above test will hang with Back trace of paca->saved_r1 (0xc00c1bc8bb00) (possibly stale) @ new_slab [ Where problems could occur ] * This is a common code change in the memory management sub-system, hence great care needs to be taken, even if it was discussed upfront at the https://lore.kernel.org/ mailing list and the upstream commit provenance shows that many eyes had a look at this. * The modification is relatively small with just one if statement (across two lines) in mm/vmscan.c. * This change is to assist 'try_to_unmap' to acquire page table locks (PTL) from the first page table entry (PTE) and to eliminate the influence of temporary and volatile PTE values. * If done wrong it can especially have a negative impact in case of large folios. and wrong hints might be given to try_to_unmap which may lead to bad page swapping. * In case of an issue with this patch the result can also be decreased performance and efficiency in the page table handling - the opposite of what the patch is supposed to address. * Fortunately several developers had their eyes on this commit, as the provenance of the patch and the discussion at LKML shows. * Further upstream conversation: Link: https://lkml.kernel.org/r/20240306095219.71086-1-21cn...@gmail.com [ Other Info ] * The commit is upstream since v6.10(-rc1), hence it will be included in oracular with the planned target kernel of 6.11. * And since (nested) KVM virtualization on ppc64el was (re-)introduced just with noble, no older Ubuntu releases older than noble are affected. __ == Comment: #0 - SEETEENA THOUFEEK - 2024-08-06 00:20:57 == +++ This bug was initially created as
[Kernel-packages] [Bug 2076675] Re: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected
** Changed in: linux (Ubuntu Oracular) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2076675 Title: [SRU][HPE 24.04] Intel FVL NIC FW flash fails with inbox driver, causing driver not detected Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Released Bug description: [Impact] Description of problem: Within 24.04 an intel FVL Idea adapter flash fails through a FW smart component RPM install. The flash successfully completes on the firmware(NVM) and fails on the firmware(ROM). The process takes roughly thirty minutes and still fails. Following this the NIC will not be recognized by the OS or RBSU until the next power cycle. Version-Release number of selected component (if applicable): Kernel 6.8.0-38-generic How reproducible: 100% of the time Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Actual results: Upgrade fails and system requires a power cycle to use NIC again. Expected results: Upgrade succeeds [Fix] Additional info: There is an upstream patch from Intel that remediates this issue, where the NIC successfully upgrades in a reasonable amount of time. https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=8b9b59e27aa88ba133fbac85def3f8be67f2d5a8 I have patched the kernel, 6.8.0-38-generic, with the patch above and observed success. [Test Plan] Steps to Reproduce: 1. Attempt to upgrade NIC (Intel Ethernet Converged Network Adapter X710-DA2 was used in my case) using upgrade located at https://support.hpe.com/connect/s/softwaredetails?language=en_US&collectionId=MTX-eeaaff922a754e17 2. Wait 30 minutes for upgrade to fail 3. Observe that NIC is no longer recognized 4. AC Power Cycle to bring the NIC back up Expected results: Upgrade succeeds [Where problems could occur] The regression risk is low [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2076675_fvl_intel_nic_fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076675/+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 2077140] Re: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server
** Changed in: linux (Ubuntu Oracular) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2077140 Title: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Released Bug description: [Impact] Add Arrow Lake H support According to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9b38cc68a03b948df1f3fcb907c7557cfc315c and https://www.phoronix.com/news/Intel-Arrow-Lake-Linux-6.9-Gfx, Intel Arrow Lake Graphics feature(Xe driver) is ready for Linux kernel 6.9. [Fix] " commit 6a9b38cc68a03b948df1f3fcb907c7557cfc315c Author: Matt Roper Date: Tue Mar 5 16:40:49 2024 -0800 drm/xe/arl: Add Arrow Lake H support ARL-H uses the same media and display IP as MTL, and a version 12.74 graphics IP (referred to as Xe_LPG+). From a driver point of view, we should be able to just treat the whole platform as MTL and rely on GRAPHICS_VERx100 checks to handle any spots where ARL's Xe_LPG+ needs different handling from MTL's Xe_LPG (i.e., workarounds). v2: Resolve conflict and Reorder PCI ids in sorted order v3: Append signed-off-by commiter to this commit Bspec: 55420 Signed-off-by: Matt Roper Signed-off-by: Dnyaneshwar Bhadane Reviewed-by: Matt Atwood Link: https://patchwork.freedesktop.org/patch/msgid/20240229070806.3402641-4 -dnyaneshwar.bhad...@intel.com diff --git a/include/drm/xe_pciids.h b/include/drm/xe_pciids.h index de1a344737bc..bc7cbef6e9d8 100644 --- a/include/drm/xe_pciids.h +++ b/include/drm/xe_pciids.h @@ -176,10 +176,13 @@ /* MTL / ARL */ #define XE_MTL_IDS(MACRO__, ...) \ MACRO__(0x7D40, ## __VA_ARGS__),\ + MACRO__(0x7D41, ## __VA_ARGS__),\ MACRO__(0x7D45, ## __VA_ARGS__),\ + MACRO__(0x7D51, ## __VA_ARGS__),\ MACRO__(0x7D55, ## __VA_ARGS__),\ MACRO__(0x7D60, ## __VA_ARGS__),\ MACRO__(0x7D67, ## __VA_ARGS__),\ + MACRO__(0x7DD1, ## __VA_ARGS__),\ MACRO__(0x7DD5, ## __VA_ARGS__) #define XE_LNL_IDS(MACRO__, ...) \ " https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/tree/include/drm/xe_pciids.h [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077140_intel_arrowlake However, the OS scope in LENOVO are ubuntu 22.04 and 24.04 server version, which are using Linux kernel 6.8, due to this reason, can this feature be backport to these two version, thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077140/+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 2077861] Re: Intel Arrow Lake IBECC feature backport request for ubuntu 22.04.5 and 24.04.1 server
** Changed in: linux (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2077861
Title:
Intel Arrow Lake IBECC feature backport request for ubuntu 22.04.5 and
24.04.1 server
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Released
Bug description:
According to
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=88150cd9501b9498e377cc4440325267c6921f90,
Intel Arrow Lake IBECC(In-Band ECC)) feature is already added in
upstream.
"
authorQiuxu Zhuo2024-06-14 11:03:54
+0800
committer Tony Luck 2024-06-14 08:08:12 -0700
commit88150cd9501b9498e377cc4440325267c6921f90 (patch)
tree fc574a0966af4f31dcc7247ff3fbbdcccffb1089
parent123b158635505c89ed0d3ef45c5845ff9030a466 (diff)
download linux-88150cd9501b9498e377cc4440325267c6921f90.tar.gz
EDAC/igen6: Add Intel Arrow Lake-U/H SoCs support
Arrow Lake-U/H SoCs share same IBECC registers with Meteor Lake-P
SoCs. Add Arrow Lake-U/H SoC compute die IDs for EDAC support.
Signed-off-by: Qiuxu Zhuo
Signed-off-by: Tony Luck
Link: https://lore.kernel.org/r/20240614030354.69180-1-qiuxu.z...@intel.com
Diffstat
-rw-r--r--drivers/edac/igen6_edac.c 8
1 files changed, 8 insertions, 0 deletions
diff --git a/drivers/edac/igen6_edac.c b/drivers/edac/igen6_edac.c
index cdd8480e736877..c9fc1e64069e33 100644
--- a/drivers/edac/igen6_edac.c
+++ b/drivers/edac/igen6_edac.c
@@ -258,6 +258,11 @@ static struct work_struct ecclog_work;
#define DID_MTL_P_SKU2 0x7d02
#define DID_MTL_P_SKU3 0x7d14
+/* Compute die IDs for Arrow Lake-UH with IBECC */
+#define DID_ARL_UH_SKU1 0x7d06
+#define DID_ARL_UH_SKU2 0x7d20
+#define DID_ARL_UH_SKU3 0x7d30
+
static int get_mchbar(struct pci_dev *pdev, u64 *mchbar)
{
union {
@@ -597,6 +602,9 @@ static const struct pci_device_id igen6_pci_tbl[] = {
{ PCI_VDEVICE(INTEL, DID_MTL_P_SKU1), (kernel_ulong_t)&mtl_p_cfg },
{ PCI_VDEVICE(INTEL, DID_MTL_P_SKU2), (kernel_ulong_t)&mtl_p_cfg },
{ PCI_VDEVICE(INTEL, DID_MTL_P_SKU3), (kernel_ulong_t)&mtl_p_cfg },
+ { PCI_VDEVICE(INTEL, DID_ARL_UH_SKU1), (kernel_ulong_t)&mtl_p_cfg },
+ { PCI_VDEVICE(INTEL, DID_ARL_UH_SKU2), (kernel_ulong_t)&mtl_p_cfg },
+ { PCI_VDEVICE(INTEL, DID_ARL_UH_SKU3), (kernel_ulong_t)&mtl_p_cfg },
{ },
};
MODULE_DEVICE_TABLE(pci, igen6_pci_tbl);
"
However, the OS scope in LENOVO are ubuntu 22.04 and 24.04 server
version, which are using Linux kernel 6.8, due to this reason, can
this feature be backport to these two version, thanks!
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077861/+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 2076190] Re: perf build disables tracepoint support
** Changed in: linux (Ubuntu Oracular) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2076190 Title: perf build disables tracepoint support Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Confirmed Status in linux source package in Oracular: Fix Released Bug description: Since commit 92550b568d, the perf build for Ubuntu kernels does not link to libtraceevent, and thus cannot perform any operations on tracepoints, including processing perf.data files that contain tracepoint events. This is a significant loss of functionality. Attempts to utilize tracepoints fail with the following: perf record -e skb:kfree_skb event syntax error: 'skb:kfree_skb' \___ unsupported tracepoint libtraceevent is necessary for tracepoint support commit 92550b568d33f82de1ac24cb912082ff31aa43ba Author: Andrea Righi Date: Tue May 30 07:27:51 2023 +0200 UBUNTU: [Packaging] perf: build without libtraceevent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076190/+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 2076406] Re: L2 Guest migration: continuously dumping while running NFS guest migration
** Changed in: linux (Ubuntu Oracular) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2076406 Title: L2 Guest migration: continuously dumping while running NFS guest migration Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Released Bug description: SRU Justification: [ Impact ] * While doing ISST testing it turned out that a 2nd level (KVM) guest (aka VM) continuously dumped when running an NFS guest migration. [ Test Plan ] * Setup two IBM Power 10 system (with firmware 1060, that offers support for KVM) with Ubuntu Server 24.04 for ppc64el. * Setup qemu/KVM on both on these system to allow guest migration. * Setup a KVM guest and place its disk on an NFS volume. * Now initiate a guest migration. * Without the two patches the initiator system will start to dump. * Since this setup requires a special firmware level, the verification will be done by the IBM Power team. [ Where problems could occur ] * Although the patch set looks huge, the patches themselves are relatively small and less invasive and I would consider them mainly as fixes. * kvmppc_set_one_reg_hv() wrongly get() the value instead of set() for MMCR3. * And The kvmppc_get_one_reg_hv() for SDAR is wrongly getting the SIAR instead of SDAR - which is quite traceable. * Then a one-reg interface for DEXCR register KVM_REG_PPC_DEXCR is introduced. Here issues can happen if the initialization is done wrong or in the case statement. A fix was added to keep nested guest DEXCR in sync. The guest state element defined for DEXCR was already there, but not really considered - this is fixed now (DEXCR GSID). If initialization was done wrong or code in case stmt, this can harm the guest state. Guest state may get out of sync. * Another one-reg register identifier was introduced that is used to read and set the virtual HASHKEYR for the guest during enter/exit with KVM_REG_PPC_HASHKEYR. Again initialization and the case code are critical. Code was added to keep nested guest HASHKEYR in sync. Again the state element defined for HASHKEYR was there, but not considered, what is fixed now (HASHKEYR GSID) If initialization was done wrong or code in case stmt, this can harm the guest state. This can harm the L2 guest during enter or exit. * Again another one-reg identifier was introduced that is used to read and set the virtual HASHPKEYR for the guest during enter/exit with KVM_REG_PPC_HASHPKEYR. And again the guest state element defined for HASHPKEYR was there but ignored which is now fixed (HASHPKEYR GSID). If initialization was done wrong or code in case stmt, this can harm the guest state. This can harm the L2 guest during enter or exit. [ Other Info ] * Since (nested) KVM support is new on P10, this does not affect older Power generation (P9 is the only other hw generation that is supported by 24.04, but it only supports native virtualization). * Both patches are upstream accepted since v6.11(-rc1), hence will be in oracular and are also upstream tagged as stable updates. * Since the required firmware FW1060 is relatively new, we can assume that not many user ran into this issue yet. __ == Comment: #0 - SEETEENA THOUFEEK - 2024-08-09 03:50:24 == +++ This bug was initially created as a clone of Bug #206737 +++ ---Problem Description--- L2 Guest migration: evelp2g4[L2]: while running NFS guest migration continuously dumping smp_call_function_many_cond+0x500/0x738 (unreliable) and watchdog: BUG: soft lockup - CPU#14 stuck for 223s! [systemd-homed} ---uname output--- NA Machine Type = NA Contact Information = NA [79205.163691] Hardware name: IBM pSeries (emulated by qemu) POWER10 (raw) 0x800200 0xf06 of:SLOF,HEAD hv:linux,kvm pSeries [79205.163834] NIP: c02bb7a4 LR: c02bb750 CTR: c00d192c [79205.163929] REGS: c003871cf1b0 TRAP: 0900 Tainted: G L [79205.165041] MSR: 8280b033 CR: 4404 XER: 20040004 [79205.165266] CFAR: IRQMASK: 0 GPR00: c02bbc58 c003871cf450 c20ded00 0009 GPR04: 0009 0009 0080 0200 GPR08: 01ff 0001 c00740f57ee0 44048222 GPR12: c00d192c c00743ddc980 GPR16: cd86e200 0
[Kernel-packages] [Bug 2076866] Re: Guest crashes post migration with migrate_misplaced_folio+0x4cc/0x5d0
** Changed in: linux (Ubuntu Oracular)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2076866
Title:
Guest crashes post migration with migrate_misplaced_folio+0x4cc/0x5d0
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Released
Bug description:
SRU Justification:
[ Impact ]
* A KVM guest (VM) that got live migrated between two Power 10 systems
(using nested virtualization, means KVM on top of PowerVM) will
highly likely crash after about an hour.
* At that point it looked like the live migration itself was already
successful, but it wasn't, and the crash is caused due to it.
[ Test Plan ]
* Setting up two Power 10 systems (with firmware level FW1060 or newer,
that supports nested KVM) with Ubuntu Server 24.04 for ppc64el.
* Setup a qemu/KVM environment that allows to live migrate a KVM
guest from one P10 system to the other.
* (The disk type does not seem to matter, hence NFS based disk storage
can be used for example).
* After about an hour the live migrated guest is likely to crash.
Hence wait for 2 hours (which increases the likeliness) and
a crash due to:
"migrate_misplaced_folio+0x540/0x5d0"
occurs.
[ Where problems could occur ]
* The 'fix' to avoid calling folio_likely_mapped_shared for cases where
folio might have already been unmapped and the move of the checks
might have an impact on page table locks if done wrong,
which may lead to wrong locks, blocked memory and finally crashes.
* The direct folio calls in mm/huge_memory.c and mm/memory.c got now
'in-directed', which may lead to a different behaviour and side-effects.
However, isolation is still done, just slightly different and
instead of using numamigrate_isolate_folio, now in (the renamed)
migrate_misplaced_folio_prepare.
* Further upstream conversations:
https://lkml.kernel.org/r/8f85c31a-e603-4578-bf49-136dae0d4...@redhat.com
https://lkml.kernel.org/r/20240626191129.658cfc32...@smtp.kernel.org
https://lkml.kernel.org/r/20240620212935.656243-3-da...@redhat.com
* Fixing a confusing return code, now to just return 0, on success is
clarifying the return code handling and usage, and was mainly done in
preparation of further changes,
but can have bad side effects if the return code was used in other
code places already as is.
* Further upstream conversations:
https://lkml.kernel.org/r/20240620212935.656243-1-da...@redhat.com
https://lkml.kernel.org/r/20240620212935.656243-2-da...@redhat.com
* Fixing the fact that NUMA balancing prohibits mTHP
(multi-size Transparent Hugepage Support) seems to be unreasonable
since its an exclusive mapping.
Allowing this seems to bring significant performance improvements
see commit message d2136d749d76), but introduced significant changes
PTE mapping and modifications and even relies on further commits:
859d4adc3415 ("mm: numa: do not trap faults on shared data section pages")
80d47f5de5e3 ("mm: don't try to NUMA-migrate COW pages that have other
uses")
This case cause issues on systems configured for THP,
may confuse the ordering, which may even lead to memory corruption.
And this may especially hit (NUMA) systems with high core numbers,
where balancing is more often needed.
* Further upstream conversations:
https://lore.kernel.org/all/20231117100745.fnpijbk4xgmal...@techsingularity.net/
https://lkml.kernel.org/r/c33a5c0b0a0323b1f8ed53772f50501f4b196e25.1712132950.git.baolin.w...@linux.alibaba.com
https://lkml.kernel.org/r/d28d276d599c26df7f38c9de8446f60e22dd1950.1711683069.git.baolin.w...@linux.alibaba.com
* The refactoring of the code for NUMA mapping rebuilding and moving
it into a new helper, seems to be straight forward, since the active code
stays unchanged, however the new function needs to be callable, but this
is the case since its all in mm/memory.c.
* Further upstream conversations:
https://lkml.kernel.org/r/cover.1712132950.git.baolin.w...@linux.alibaba.com
https://lkml.kernel.org/r/cover.1711683069.git.baolin.w...@linux.alibaba.com
https://lkml.kernel.org/r/8bc2586bdd8dbbe6d83c09b77b360ec8fcac3736.1711683069.git.baolin.w...@linux.alibaba.com
* The refactoring of folio_estimated_sharers to folio_likely_mapped_shared
is more significant, since the logic changed from
(folio_estimated_sharers) 'estimate the number of sharers of a folio' to
(folio_likely_mapped_shared) 'estimate if the folio is mapped into the page
tables of more than one MM'.
* Since th
[Kernel-packages] [Bug 2077140] Re: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server
you probably want this instead: Author: Matt Roper 2024-01-08 14:27:36 Committer: Matt Roper 2024-01-19 01:24:32 Tags: cod/tip/drm-intel-next/2024-01-19 Parent: a99d453d245960b82b5c6e7ce868815898b1ca23 (drm/i915/opregion: remove unused lid_state) Branches: master, remotes/origin/master and many more (46) Follows: cod/tip/drm-intel-next/2024-01-18 Precedes: cod/tip/drm-intel-next/2024-01-20 drm/i915: Add additional ARL PCI IDs -- 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/2077140 Title: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Committed Bug description: [Impact] Add Arrow Lake H support According to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9b38cc68a03b948df1f3fcb907c7557cfc315c and https://www.phoronix.com/news/Intel-Arrow-Lake-Linux-6.9-Gfx, Intel Arrow Lake Graphics feature(Xe driver) is ready for Linux kernel 6.9. [Fix] " commit 6a9b38cc68a03b948df1f3fcb907c7557cfc315c Author: Matt Roper Date: Tue Mar 5 16:40:49 2024 -0800 drm/xe/arl: Add Arrow Lake H support ARL-H uses the same media and display IP as MTL, and a version 12.74 graphics IP (referred to as Xe_LPG+). From a driver point of view, we should be able to just treat the whole platform as MTL and rely on GRAPHICS_VERx100 checks to handle any spots where ARL's Xe_LPG+ needs different handling from MTL's Xe_LPG (i.e., workarounds). v2: Resolve conflict and Reorder PCI ids in sorted order v3: Append signed-off-by commiter to this commit Bspec: 55420 Signed-off-by: Matt Roper Signed-off-by: Dnyaneshwar Bhadane Reviewed-by: Matt Atwood Link: https://patchwork.freedesktop.org/patch/msgid/20240229070806.3402641-4 -dnyaneshwar.bhad...@intel.com diff --git a/include/drm/xe_pciids.h b/include/drm/xe_pciids.h index de1a344737bc..bc7cbef6e9d8 100644 --- a/include/drm/xe_pciids.h +++ b/include/drm/xe_pciids.h @@ -176,10 +176,13 @@ /* MTL / ARL */ #define XE_MTL_IDS(MACRO__, ...) \ MACRO__(0x7D40, ## __VA_ARGS__),\ + MACRO__(0x7D41, ## __VA_ARGS__),\ MACRO__(0x7D45, ## __VA_ARGS__),\ + MACRO__(0x7D51, ## __VA_ARGS__),\ MACRO__(0x7D55, ## __VA_ARGS__),\ MACRO__(0x7D60, ## __VA_ARGS__),\ MACRO__(0x7D67, ## __VA_ARGS__),\ + MACRO__(0x7DD1, ## __VA_ARGS__),\ MACRO__(0x7DD5, ## __VA_ARGS__) #define XE_LNL_IDS(MACRO__, ...) \ " https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/tree/include/drm/xe_pciids.h [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077140_intel_arrowlake However, the OS scope in LENOVO are ubuntu 22.04 and 24.04 server version, which are using Linux kernel 6.8, due to this reason, can this feature be backport to these two version, thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077140/+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 2077140] Re: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server
ARL uses i915 by default. LNL is the first one to default to xe. -- 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/2077140 Title: [SRU]Intel Arrow Lake Graphics feature backport request for ubuntu 22.04.5 and 24.04 server Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: In Progress Status in linux source package in Oracular: Fix Committed Bug description: [Impact] Add Arrow Lake H support According to https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a9b38cc68a03b948df1f3fcb907c7557cfc315c and https://www.phoronix.com/news/Intel-Arrow-Lake-Linux-6.9-Gfx, Intel Arrow Lake Graphics feature(Xe driver) is ready for Linux kernel 6.9. [Fix] " commit 6a9b38cc68a03b948df1f3fcb907c7557cfc315c Author: Matt Roper Date: Tue Mar 5 16:40:49 2024 -0800 drm/xe/arl: Add Arrow Lake H support ARL-H uses the same media and display IP as MTL, and a version 12.74 graphics IP (referred to as Xe_LPG+). From a driver point of view, we should be able to just treat the whole platform as MTL and rely on GRAPHICS_VERx100 checks to handle any spots where ARL's Xe_LPG+ needs different handling from MTL's Xe_LPG (i.e., workarounds). v2: Resolve conflict and Reorder PCI ids in sorted order v3: Append signed-off-by commiter to this commit Bspec: 55420 Signed-off-by: Matt Roper Signed-off-by: Dnyaneshwar Bhadane Reviewed-by: Matt Atwood Link: https://patchwork.freedesktop.org/patch/msgid/20240229070806.3402641-4 -dnyaneshwar.bhad...@intel.com diff --git a/include/drm/xe_pciids.h b/include/drm/xe_pciids.h index de1a344737bc..bc7cbef6e9d8 100644 --- a/include/drm/xe_pciids.h +++ b/include/drm/xe_pciids.h @@ -176,10 +176,13 @@ /* MTL / ARL */ #define XE_MTL_IDS(MACRO__, ...) \ MACRO__(0x7D40, ## __VA_ARGS__),\ + MACRO__(0x7D41, ## __VA_ARGS__),\ MACRO__(0x7D45, ## __VA_ARGS__),\ + MACRO__(0x7D51, ## __VA_ARGS__),\ MACRO__(0x7D55, ## __VA_ARGS__),\ MACRO__(0x7D60, ## __VA_ARGS__),\ MACRO__(0x7D67, ## __VA_ARGS__),\ + MACRO__(0x7DD1, ## __VA_ARGS__),\ MACRO__(0x7DD5, ## __VA_ARGS__) #define XE_LNL_IDS(MACRO__, ...) \ " https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/tree/include/drm/xe_pciids.h [Where problems could occur] [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077140_intel_arrowlake However, the OS scope in LENOVO are ubuntu 22.04 and 24.04 server version, which are using Linux kernel 6.8, due to this reason, can this feature be backport to these two version, thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077140/+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 2080624] Re: Remove from oracular, EOL upstream
Removing packages from oracular: libnvidia-nscq-470 470.256.02-0ubuntu1 in oracular libnvidia-nscq-460 470.256.02-0ubuntu1 in oracular amd64 libnvidia-nscq-470 470.256.02-0ubuntu1 in oracular amd64 Comment: LP:#2080624 Remove [y|N]? y 1 package successfully removed. ** Changed in: libnvidia-nscq-470 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2080624 Title: Remove from oracular, EOL upstream Status in fabric-manager-470 package in Ubuntu: Fix Released Status in libnvidia-nscq-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Bug description: This driver is EOL now, so it should be removed from oracular. https://endoflife.date/nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/2080624/+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 2080624] Re: Remove from oracular, EOL upstream
** Also affects: libnvidia-nscq-470 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2080624 Title: Remove from oracular, EOL upstream Status in fabric-manager-470 package in Ubuntu: Fix Released Status in libnvidia-nscq-470 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Bug description: This driver is EOL now, so it should be removed from oracular. https://endoflife.date/nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/2080624/+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 2081723] Re: libnvidia-compute-560 should provide libcuda1
** Also affects: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-550-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2081723 Title: libnvidia-compute-560 should provide libcuda1 Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Status in nvidia-graphics-drivers-550-server package in Ubuntu: New Status in nvidia-graphics-drivers-560 package in Ubuntu: New Bug description: the gpu-burn package is uninstallable, because libnivida-compute stopped providing the libcuda1 virtual package. Please re-add that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2081723/+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 2073274] Re: 2024.07.04 new upstream release
Hello Noah, or anyone else affected, Accepted wireless-regdb into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wireless- regdb/2024.07.04-0ubuntu1~24.04.1 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. ** Changed in: wireless-regdb (Ubuntu Noble) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-noble -- 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/2073274 Title: 2024.07.04 new upstream release Status in wireless-regdb package in Ubuntu: Fix Released 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: Fix Committed Status in wireless-regdb source package in Oracular: Fix Released 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/2073274/+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 2080969] Re: "dmic_num" parameter in snd_sof_intel_hda_common module stopped working in kernel 6.11 (worked in 6.8)
commit 6fe61f31eab1ec84c385786cd052415d966e5235 Author: Pierre-Louis Bossart Date: Fri May 3 08:52:21 2024 -0500 ASoC: SOF: Intel: move hda.c to different module -- 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/2080969 Title: "dmic_num" parameter in snd_sof_intel_hda_common module stopped working in kernel 6.11 (worked in 6.8) Status in linux package in Ubuntu: Invalid Status in linux source package in Oracular: Invalid Bug description: Hi, in order to fix the audio input of my Toshiba Portege X30 i had to pass this kernel parameter (worked in kernel 6.8.0-44) options snd_sof_intel_hda_common dmic_num=4 However, after upgrading to Ubuntu 24.10 with kernel 6.11.0-7 the parameter "dmic_num" is not recognized, so i can't fix the audio input this way. The error showed is as follows: snd_sof_intel_hda_common: unknown parameter 'dmic_num' ignored Perhaps the parameter is now replaced by another one in 6.11? ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-7-generic 6.11.0-7.7 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:ramses 2020 F pipewire /dev/snd/controlC0: ramses 2020 F pipewire ramses 2024 F wireplumber CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 17 17:30:01 2024 InstallationDate: Installed on 2023-08-11 (403 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dynabook Inc. PORTEGE X30W-K ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-7-generic root=UUID=ad54828e-07ad-4a56-9605-bc9316aa8014 ro recovery nomodeset dis_ucode_ldr quiet splash lsm=ndlock,lockdown,yama,integrity,apparmor,bpf PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.11.0-7-generic N/A linux-backports-modules-6.11.0-7-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to oracular on 2024-09-16 (1 days ago) dmi.bios.date: 02/17/2023 dmi.bios.release: 3.30 dmi.bios.vendor: Dynabook Inc. dmi.bios.version: Version 3.30 dmi.board.asset.tag: 00 dmi.board.name: OK0118/ dmi.board.vendor: Dynabook Inc. dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 31 dmi.chassis.vendor: Dynabook Inc. dmi.chassis.version: Version 1.0 dmi.ec.firmware.release: 2.10 dmi.modalias: dmi:bvnDynabookInc.:bvrVersion3.30:bd02/17/2023:br3.30:efr2.10:svnDynabookInc.:pnPORTEGEX30W-K:pvrPDA31E-0FS033CE:rvnDynabookInc.:rnOK0118/:rvrVersionA0:cvnDynabookInc.:ct31:cvrVersion1.0:skuPDA31E: dmi.product.family: PORTEGE dmi.product.name: PORTEGE X30W-K dmi.product.sku: PDA31E dmi.product.version: PDA31E-0FS033CE dmi.sys.vendor: Dynabook Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080969/+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 2080949] Re: lubuntu oracular 6.11 kernel; 1 display 'cannot display' & unusable on LIVE
** Also affects: linux (Ubuntu Oracular) 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/2080949 Title: lubuntu oracular 6.11 kernel; 1 display 'cannot display' & unusable on LIVE Status in linux package in Ubuntu: New Status in linux source package in Oracular: New Bug description: Lubuntu oracular live; first daily using 6.11 kernel on this box which I think is the key difference. On boot (this is second boot of this ISO) I get on one display a message 1: Auto Detect (Digital Input) Cannot Display This Video Model Optimum resolution 1280x1024 60Hz and display was not usable. The other display works... ** Expected results I can use both displays; like I did earlier today OR do if I boot installed systems (Ubuntu noble, oracular [6.8], jammy, Debian testing) ** Actual results I'm limited to one display only; second shows a message & my LXQt.Monitor.Settings won't let me use the display.. ** Other thoughts - booting this ISO in live mode & using `lshw -C video`, and comparing with installed systems I don't see any differences; I can save & append the results if helpful (I didn't save them & was relying on my bad.memory.. so not conclusive) - I have no issues on NOBLE, JAMMY installs; and hadn't noticed any on ORACULAR install either; but installed system was still on 6.8 kernel... I booted the INSTALLED ORACULAR; applied `apt update; apt full- upgrade`, when done rebooted and IT HAD THE SAME ISSUE as this live system This is the first time I've experienced this. This video card is OLD!! and I'm suspicious issue is this real old video car AND newer kernel; not Ubuntu specific issue; but bug report allows tracking into future (subsequent ISOs etc) Users with old hardware like this can still use Ubuntu 24.04 LTS and use the GA kernel stack??.. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-7-generic 6.11.0-7.7 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:lubuntu1857 F pipewire /dev/snd/controlC1: lubuntu1860 F wireplumber /dev/snd/controlC0: lubuntu1860 F wireplumber CasperMD5CheckResult: pass CasperVersion: 1.502 CurrentDesktop: LXQt Date: Tue Sep 17 11:15:18 2024 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' LiveMediaBuild: Lubuntu 24.10 "Oracular Oriole" - Daily amd64 (20240916) MachineType: Dell Inc. OptiPlex 780 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.11.0-7-generic N/A linux-backports-modules-6.11.0-7-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2010 dmi.bios.release: 3.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0200DY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/13/2010:br3.0:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0200DY:rvrA00:cvnDellInc.:ct3:cvr:sku: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080949/+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 2080969] Re: "dmic_num" parameter in snd_sof_intel_hda_common module stopped working in kernel 6.11 (worked in 6.8)
the module got renamed as snd_sof_intel_hda_generic ** Changed in: linux (Ubuntu Oracular) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2080969 Title: "dmic_num" parameter in snd_sof_intel_hda_common module stopped working in kernel 6.11 (worked in 6.8) Status in linux package in Ubuntu: Invalid Status in linux source package in Oracular: Invalid Bug description: Hi, in order to fix the audio input of my Toshiba Portege X30 i had to pass this kernel parameter (worked in kernel 6.8.0-44) options snd_sof_intel_hda_common dmic_num=4 However, after upgrading to Ubuntu 24.10 with kernel 6.11.0-7 the parameter "dmic_num" is not recognized, so i can't fix the audio input this way. The error showed is as follows: snd_sof_intel_hda_common: unknown parameter 'dmic_num' ignored Perhaps the parameter is now replaced by another one in 6.11? ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-7-generic 6.11.0-7.7 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:ramses 2020 F pipewire /dev/snd/controlC0: ramses 2020 F pipewire ramses 2024 F wireplumber CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 17 17:30:01 2024 InstallationDate: Installed on 2023-08-11 (403 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dynabook Inc. PORTEGE X30W-K ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-7-generic root=UUID=ad54828e-07ad-4a56-9605-bc9316aa8014 ro recovery nomodeset dis_ucode_ldr quiet splash lsm=ndlock,lockdown,yama,integrity,apparmor,bpf PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.11.0-7-generic N/A linux-backports-modules-6.11.0-7-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to oracular on 2024-09-16 (1 days ago) dmi.bios.date: 02/17/2023 dmi.bios.release: 3.30 dmi.bios.vendor: Dynabook Inc. dmi.bios.version: Version 3.30 dmi.board.asset.tag: 00 dmi.board.name: OK0118/ dmi.board.vendor: Dynabook Inc. dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 31 dmi.chassis.vendor: Dynabook Inc. dmi.chassis.version: Version 1.0 dmi.ec.firmware.release: 2.10 dmi.modalias: dmi:bvnDynabookInc.:bvrVersion3.30:bd02/17/2023:br3.30:efr2.10:svnDynabookInc.:pnPORTEGEX30W-K:pvrPDA31E-0FS033CE:rvnDynabookInc.:rnOK0118/:rvrVersionA0:cvnDynabookInc.:ct31:cvrVersion1.0:skuPDA31E: dmi.product.family: PORTEGE dmi.product.name: PORTEGE X30W-K dmi.product.sku: PDA31E dmi.product.version: PDA31E-0FS033CE dmi.sys.vendor: Dynabook Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080969/+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 2080969] Re: "dmic_num" parameter in snd_sof_intel_hda_common module stopped working in kernel 6.11 (worked in 6.8)
** Also affects: linux (Ubuntu Oracular) Importance: Undecided Status: Confirmed -- 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/2080969 Title: "dmic_num" parameter in snd_sof_intel_hda_common module stopped working in kernel 6.11 (worked in 6.8) Status in linux package in Ubuntu: Confirmed Status in linux source package in Oracular: Confirmed Bug description: Hi, in order to fix the audio input of my Toshiba Portege X30 i had to pass this kernel parameter (worked in kernel 6.8.0-44) options snd_sof_intel_hda_common dmic_num=4 However, after upgrading to Ubuntu 24.10 with kernel 6.11.0-7 the parameter "dmic_num" is not recognized, so i can't fix the audio input this way. The error showed is as follows: snd_sof_intel_hda_common: unknown parameter 'dmic_num' ignored Perhaps the parameter is now replaced by another one in 6.11? ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: linux-image-6.11.0-7-generic 6.11.0-7.7 ProcVersionSignature: Ubuntu 6.11.0-7.7-generic 6.11.0-rc7 Uname: Linux 6.11.0-7-generic x86_64 ApportVersion: 2.30.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:ramses 2020 F pipewire /dev/snd/controlC0: ramses 2020 F pipewire ramses 2024 F wireplumber CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Sep 17 17:30:01 2024 InstallationDate: Installed on 2023-08-11 (403 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Dynabook Inc. PORTEGE X30W-K ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-7-generic root=UUID=ad54828e-07ad-4a56-9605-bc9316aa8014 ro recovery nomodeset dis_ucode_ldr quiet splash lsm=ndlock,lockdown,yama,integrity,apparmor,bpf PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.11.0-7-generic N/A linux-backports-modules-6.11.0-7-generic N/A linux-firmware20240913.gita34e7a5f-0ubuntu2 SourcePackage: linux UpgradeStatus: Upgraded to oracular on 2024-09-16 (1 days ago) dmi.bios.date: 02/17/2023 dmi.bios.release: 3.30 dmi.bios.vendor: Dynabook Inc. dmi.bios.version: Version 3.30 dmi.board.asset.tag: 00 dmi.board.name: OK0118/ dmi.board.vendor: Dynabook Inc. dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 31 dmi.chassis.vendor: Dynabook Inc. dmi.chassis.version: Version 1.0 dmi.ec.firmware.release: 2.10 dmi.modalias: dmi:bvnDynabookInc.:bvrVersion3.30:bd02/17/2023:br3.30:efr2.10:svnDynabookInc.:pnPORTEGEX30W-K:pvrPDA31E-0FS033CE:rvnDynabookInc.:rnOK0118/:rvrVersionA0:cvnDynabookInc.:ct31:cvrVersion1.0:skuPDA31E: dmi.product.family: PORTEGE dmi.product.name: PORTEGE X30W-K dmi.product.sku: PDA31E dmi.product.version: PDA31E-0FS033CE dmi.sys.vendor: Dynabook Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080969/+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 2080853] Re: oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs
** Also affects: linux (Ubuntu Oracular) Importance: High 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/2080853 Title: oracular 6.11 kernel regression with ext4 and ea_inode mount flags and exercising xattrs Status in Linux: Confirmed Status in linux package in Ubuntu: New Status in linux source package in Oracular: New Bug description: How to reproduce this issue: Kernel: 6.11.0-7, AMD64 virtual machine, oracular, updated 16th Sept 2024 @ 14:15 UK TZ 8 thread virtual machine (important, must be multiple CPU threads to trigger the regression) 20GB virtio drive on /dev/vdb, 1 partition /dev/vdb1 sudo mkfs.ext4 /dev/vdb1 -O ea_inode sudo mount /dev/vdb1 /mnt git clone https://github.com/ColinIanKing/stress-ng cd stress-ng make clean; make -j $(nproc) ..wait a couple of minutes, you will see that the number of running processes is not 8 as expected (from the --vmstat output of stress-ng) cannot stop stress-ng because of a kernel lockup; so use another tty and check dmesg, I get the following: [ 247.028846] INFO: task jbd2/vdb1-8:1548 blocked for more than 122 seconds. [ 247.030830] Not tainted 6.11.0-7-generic #7-Ubuntu [ 247.032667] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 247.034170] task:jbd2/vdb1-8 state:D stack:0 pid:1548 tgid:1548 ppid:2 flags:0x4000 [ 247.034176] Call Trace: [ 247.034178] [ 247.034182] __schedule+0x277/0x6c0 [ 247.034199] schedule+0x29/0xd0 [ 247.034203] jbd2_journal_wait_updates+0x77/0xf0 [ 247.034207] ? __pfx_autoremove_wake_function+0x10/0x10 [ 247.034213] jbd2_journal_commit_transaction+0x290/0x1a10 [ 247.034223] kjournald2+0xa8/0x250 [ 247.034228] ? __pfx_autoremove_wake_function+0x10/0x10 [ 247.034233] ? __pfx_kjournald2+0x10/0x10 [ 247.034236] kthread+0xe1/0x110 [ 247.034241] ? __pfx_kthread+0x10/0x10 [ 247.034244] ret_from_fork+0x44/0x70 [ 247.034247] ? __pfx_kthread+0x10/0x10 [ 247.034251] ret_from_fork_asm+0x1a/0x30 [ 247.034257] NOTE: this works fine for Limux 6.8.0-31, so this looks like a regression for 6.11.0-7 Attached is the full kernel log. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2080853/+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 2080214] Please test proposed package
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20240318.git3b128b60-0ubuntu2.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 linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2080214
Title:
Missing DMC firmware for Xe driver for Intel BattleMage
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-firmware source package in Oracular:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing DMC firmware for Xe driver for Intel BattleMage.
```
xe :04:00.0: Direct firmware load for i915/bmg_dmc.bin failed with error
-2
xe :04:00.0: [drm] Failed to load DMC firmware i915/bmg_dmc.bin
(-ENOENT). Disabling runtime power management.
```
[Fix]
linux-firmware commit fa86949f1 ("i915: Add BMG DMC v2.06") included
in upstream tag 20240513.
[Test Case]
Expect following messages in dmesg output:
```
$ sudo dmesg | grep xe
xe :04:00.0: [drm] Finished loading DMC firmware i915/bmg_dmc.bin (v2.6)
```
[Where problems could occur]
New hardware. May need further updates.
[Other Info]
Targets v6.11+ kernels, so nominating only for Noble and Oracular.
= original bug description ==
[5.146422] xe :04:00.0: Direct firmware load for i915/bmg_dmc.bin
failed with error -2
[5.146424] xe :04:00.0: [drm] Failed to load DMC firmware
i915/bmg_dmc.bin (-ENOENT). Disabling runtime power management.
[5.146426] xe :04:00.0: [drm] DMC firmware homepage:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
Need linux-firmware commit fa86949f1 ("i915: Add BMG DMC v2.06")
included in upstream tag 20240513.
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:u 2277 F pipewire
/dev/snd/controlC0: u 2280 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
Dependencies: firmware-sof-signed 2023.12.1-1ubuntu1
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2024-05-03 (131 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240314)
MachineType: Intel Corporation Arrow Lake Client Platform
Package: linux-firmware
PackageArchitecture: amd64
ProcFB: 0 xedrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-1004-oem
root=UUID=cf746c14-f32e-47c6-aafb-6f133166eacc ro i915.force_probe=!*
xe.force_probe=* quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.11.0-1004.4-oem 6.11.0-rc6
RelatedPackageVersions:
linux-restricted-modules-6.11.0-1004-oem N/A
linux-backports-modules-6.11.0-1004-oem N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.2
Tags: noble
Uname: Linux 6.11.0-1004-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 01/31/2024
dmi.bios.vendor: Intel Corporation
dmi.bios.version: MTLSFWI1.R00.4052.D81.2401311921
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: MTL-S UDIMM 1DPC EVCRB
dmi.board.vendor: Intel Corporation
dmi.board.version: 3
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.ec.firmware.release: 2.19
dmi.modalias:
dmi:bvnIntelCorporation:bvrMTLSFWI1.R00.4052.D81.2401311921:bd01/31/2024:efr2.19:svnIntelCorporation:pnArrowLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnMTL-SUDIMM1DPCEVCRB:rvr3:cvnIntelCorporation:ct3:cvr0.1:sku010010210200:
dmi.product.family: Arrow Lake Client System
dmi.pr
[Kernel-packages] [Bug 2071698] Re: Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20240318.git3b128b60-0ubuntu2.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.
** Changed in: linux-firmware (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/2071698
Title:
Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-oem-6.11 source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Committed
Status in linux-firmware source package in Oracular:
Fix Released
Status in linux-oem-6.11 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
[Impact]
Starting from Intel Lunar Lake, the ISH firmware will reside in system
root as separated blobs, and the kernel driver is responsible for
loading a preferred one based on DMI info.
[Fix]
Kernel fixes in linux-next:
* aa4674c525e1e hid: intel-ish-hid: Add support for vendor customized
firmware loading
* 641361538b68d HID: intel-ish-hid: Use CPU generation string in driver_data
* 87de1615194ee Documentation: hid: intel-ish-hid: Add vendor custom firmware
loading
linux-firmware in upstream tag 20240709:
* 33a8b2a7f604 linux-firmware: Add ISH firmware file for Intel Lunar Lake
platform
[Test Case]
dmesg dumps:
```
intel_ish_ipc :00:12.0: ISH loader: firmware loaded. size:748032
ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done
OK, num_hid_devices=2
hid-generic 001F:8087:0AC2.0005: hidraw4: SENSOR HUB HID v2.00 Device
[hid-ishtp 8087:0AC2] on
hid-generic 001F:8087:0AC2.0006: hidraw5: SENSOR HUB HID v2.00 Device
[hid-ishtp 8087:0AC2] on
hid-sensor-hub 001F:8087:0AC2.0005: hidraw4: SENSOR HUB HID v2.00 Device
[hid-ishtp 8087:0AC2] on
hid-sensor-hub 001F:8087:0AC2.0006: hidraw5: SENSOR HUB HID v2.00 Device
[hid-ishtp 8087:0AC2] on
```
[Where problems could occur]
This is to include generic blob provided by Intel for all Lunar Lake
platforms. It may not be stable, may not be functional, and may have
various problems until the hardware vendor submit their own.
[Other Info]
Nominated for linux/oracular, linux-oem-6.11/noble, linux-
firmware/oracular and linux-firmware/noble.
== original bug report ==
* kernel
-
https://patchwork.kernel.org/project/linux-input/cover/20240813034736.812475-1-lixu.zh...@intel.com/
* linux-firmware
- generic
* commit 33a8b2a7f604 ("linux-firmware: Add ISH firmware file for Intel
Lunar Lake platform")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2071698/+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 2079024] Re: Update mt7925 BT FW to avoid bluetooth_obex_send failed
Hello En-Wei, or anyone else affected, Accepted linux-firmware into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20240318.git3b128b60-0ubuntu2.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. ** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- 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/2079024 Title: Update mt7925 BT FW to avoid bluetooth_obex_send failed Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Committed Bug description: [Impact] In OEM project, we found that the Mediatek mtk7925 bluetooth device will fail on transmitting files with the peer device by OBEX. The bluetooth mouse, keyboard and headset are working while this happen. [Fix] Cherry-pick the mediatek/mt7925/BT_RAM_CODE_MT7925_1_1_hdr.bin from the linux-firmware:Oracular: https://kernel.ubuntu.com/gitea/kernel/linux- firmware/commit/79c19bb0cda0abc97fdca49d3165f3b419aa2ac6 [Test Plan] 1. Boot into OS 2. checkbox-cli run com.canonical.certification::bluetooth/bluetooth_obex_send [Where problems could occur] May cause regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2079024/+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 2080428] Please test proposed package
Hello Maximilian, or anyone else affected, Accepted linux-firmware into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20240318.git3b128b60-0ubuntu2.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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2080428 Title: Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Committed Status in linux-firmware source package in Oracular: Fix Committed Bug description: [Impact] After installing new package updates as suggested by ubuntu, my WiFi Card (Qualcomm WCN785x Wi-Fi 7(802.11be) as far as lshw -C network is concerned) did not connect to the network again after waking the laptop from idle. After some research I found this bug report: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2077296 It seems that after updating the firmware package after the bugfix for the mentioned bug got released, the updated file board-2.bin is now broken for at least T14 Gen5 AMD. In the mentioned bugfix thread, a person already posted this issue yesterday. However, I am reposting it here as suggested by Timo in https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2077296/comments/5. Running sudo dmesg | grep ath12k reveals that the board data could not be fetched from the updated file: [2.381547] ath12k_pci :02:00.0: BAR 0 [mem 0x9060-0x907f 64bit]: assigned [2.381567] ath12k_pci :02:00.0: enabling device ( -> 0002) [2.382640] ath12k_pci :02:00.0: MSI vectors: 16 [2.382647] ath12k_pci :02:00.0: Hardware name: wcn7850 hw2.0 [3.479946] ath12k_pci :02:00.0: chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200 [3.479950] ath12k_pci :02:00.0: fw_version 0x100301e1 fw_build_timestamp 2023-12-06 04:05 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 [3.492086] ath12k_pci :02:00.0: failed to fetch board data for bus=pci,vendor=17cb,device=1107,subsystem-vendor=17aa,subsystem-device=e0e6,qmi-chip-id=2,qmi-board-id=255 from ath12k/WCN7850/hw2.0/board-2.bin [3.492101] ath12k_pci :02:00.0: failed to fetch board.bin from WCN7850/hw2.0 [3.492103] ath12k_pci :02:00.0: qmi failed to load bdf: [3.492105] ath12k_pci :02:00.0: qmi failed to load board data file:-2 Any help is greatly appreciated. [Fix] Revert offending commit. [Where Problems Could Occur] Limited to ath12k wifi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2080428/+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 2080371] Please test proposed package
Hello Anson, or anyone else affected, Accepted linux-firmware into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20240318.git3b128b60-0ubuntu2.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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2080371 Title: Add firmware for Cirrus CS35L54 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Noble: Fix Committed Status in linux-firmware source package in Oracular: Fix Released Bug description: [Impact] Without the FWs loaded, the audio output missing [ 7.103847] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.0: .bin file required but not found [ 7.103852] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.1: .bin file required but not found [ 7.103853] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.2: .bin file required but not found [ 7.103855] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.3: .bin file required but not found [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=a9c9dbf495fd3aa6e880b2ba32af576f83e7f7fa [Test Case] With the FWs loaded, the audio output properly [ 715.179244] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.2: DSP1: Firmware: 1a00d6 vendor: 0x2 v3.11.18, 41 algorithms [ 715.553139] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.0: DSP1: Firmware: 1a00d6 vendor: 0x2 v3.11.18, 41 algorithms [ 715.554366] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.1: DSP1: Firmware: 1a00d6 vendor: 0x2 v3.11.18, 41 algorithms [ 715.555907] cs35l56-hda i2c-CSC3554:00-cs35l54-hda.3: DSP1: Firmware: 1a00d6 vendor: 0x2 v3.11.18, 41 algorithms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2080371/+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 2080624] Re: Remove from oracular, EOL upstream
Removing packages from oracular: nvidia-graphics-drivers-470 470.256.02-0ubuntu2 in oracular libnvidia-cfg1-460 470.256.02-0ubuntu2 in oracular amd64 libnvidia-cfg1-465 470.256.02-0ubuntu2 in oracular amd64 libnvidia-cfg1-470 470.256.02-0ubuntu2 in oracular amd64 libnvidia-common-460 470.256.02-0ubuntu2 in oracular amd64 libnvidia-common-460 470.256.02-0ubuntu2 in oracular arm64 libnvidia-common-460 470.256.02-0ubuntu2 in oracular armhf libnvidia-common-460 470.256.02-0ubuntu2 in oracular i386 libnvidia-common-460 470.256.02-0ubuntu2 in oracular ppc64el libnvidia-common-460 470.256.02-0ubuntu2 in oracular riscv64 libnvidia-common-460 470.256.02-0ubuntu2 in oracular s390x libnvidia-common-465 470.256.02-0ubuntu2 in oracular amd64 libnvidia-common-465 470.256.02-0ubuntu2 in oracular arm64 libnvidia-common-465 470.256.02-0ubuntu2 in oracular armhf libnvidia-common-465 470.256.02-0ubuntu2 in oracular i386 libnvidia-common-465 470.256.02-0ubuntu2 in oracular ppc64el libnvidia-common-465 470.256.02-0ubuntu2 in oracular riscv64 libnvidia-common-465 470.256.02-0ubuntu2 in oracular s390x libnvidia-common-470 470.256.02-0ubuntu2 in oracular amd64 libnvidia-common-470 470.256.02-0ubuntu2 in oracular arm64 libnvidia-common-470 470.256.02-0ubuntu2 in oracular armhf libnvidia-common-470 470.256.02-0ubuntu2 in oracular i386 libnvidia-common-470 470.256.02-0ubuntu2 in oracular ppc64el libnvidia-common-470 470.256.02-0ubuntu2 in oracular riscv64 libnvidia-common-470 470.256.02-0ubuntu2 in oracular s390x libnvidia-compute-460 470.256.02-0ubuntu2 in oracular amd64 libnvidia-compute-460 470.256.02-0ubuntu2 in oracular i386 libnvidia-compute-465 470.256.02-0ubuntu2 in oracular amd64 libnvidia-compute-465 470.256.02-0ubuntu2 in oracular i386 libnvidia-compute-470 470.256.02-0ubuntu2 in oracular amd64 libnvidia-compute-470 470.256.02-0ubuntu2 in oracular i386 libnvidia-decode-460 470.256.02-0ubuntu2 in oracular amd64 libnvidia-decode-460 470.256.02-0ubuntu2 in oracular i386 libnvidia-decode-465 470.256.02-0ubuntu2 in oracular amd64 libnvidia-decode-465 470.256.02-0ubuntu2 in oracular i386 libnvidia-decode-470 470.256.02-0ubuntu2 in oracular amd64 libnvidia-decode-470 470.256.02-0ubuntu2 in oracular i386 libnvidia-encode-460 470.256.02-0ubuntu2 in oracular amd64 libnvidia-encode-460 470.256.02-0ubuntu2 in oracular i386 libnvidia-encode-465 470.256.02-0ubuntu2 in oracular amd64 libnvidia-encode-465 470.256.02-0ubuntu2 in oracular i386 libnvidia-encode-470 470.256.02-0ubuntu2 in oracular amd64 libnvidia-encode-470 470.256.02-0ubuntu2 in oracular i386 libnvidia-extra-460 470.256.02-0ubuntu2 in oracular amd64 libnvidia-extra-460 470.256.02-0ubuntu2 in oracular i386 libnvidia-extra-465 470.256.02-0ubuntu2 in oracular amd64 libnvidia-extra-465 470.256.02-0ubuntu2 in oracular i386 libnvidia-extra-470 470.256.02-0ubuntu2 in oracular amd64 libnvidia-extra-470 470.256.02-0ubuntu2 in oracular i386 libnvidia-fbc1-460 470.256.02-0ubuntu2 in oracular amd64 libnvidia-fbc1-460 470.256.02-0ubuntu2 in oracular i386 libnvidia-fbc1-465 470.256.02-0ubuntu2 in oracular amd64 libnvidia-fbc1-465 470.256.02-0ubuntu2 in oracular i386 libnvidia-fbc1-470 470.256.02-0ubuntu2 in oracular amd64 libnvidia-fbc1-470 470.256.02-0ubuntu2 in oracular i386 libnvidia-gl-460 470.256.02-0ubuntu2 in oracular amd64 libnvidia-gl-460 470.256.02-0ubuntu2 in oracular i386 libnvidia-gl-465 470.256.02-0ubuntu2 in oracular amd64 libnvidia-gl-465 470.256.02-0ubuntu2 in oracular i386 libnvidia-gl-470 470.256.02-0ubuntu2 in oracular amd64 libnvidia-gl-470 470.256.02-0ubuntu2 in oracular i386 libnvidia-ifr1-460 470.256.02-0ubuntu2 in oracular amd64 libnvidia-ifr1-460 470.256.02-0ubuntu2 in oracular i386 libnvidia-ifr1-465 470.256.02-0ubuntu2 in oracular amd64 libnvidia-ifr1-465 470.256.02-0ubuntu2 in oracular i386 libnvidia-ifr1-470 470.256.02-0ubuntu2 in oracular amd64 libnvidia-ifr1-470 470.256.02-0ubuntu2 in oracular i386
[Kernel-packages] [Bug 2080624] Re: Remove from oracular, EOL upstream
Removing packages from oracular: fabric-manager-470 470.256.02-0ubuntu1 in oracular cuda-drivers-fabricmanager-460 470.256.02-0ubuntu1 in oracular amd64 cuda-drivers-fabricmanager-470 470.256.02-0ubuntu1 in oracular amd64 nvidia-fabricmanager-460 470.256.02-0ubuntu1 in oracular amd64 nvidia-fabricmanager-470 470.256.02-0ubuntu1 in oracular amd64 nvidia-fabricmanager-dev-460 470.256.02-0ubuntu1 in oracular amd64 nvidia-fabricmanager-dev-470 470.256.02-0ubuntu1 in oracular amd64 Comment: lp#2080624 Remove [y|N]? y 1 package successfully removed. ** Changed in: fabric-manager-470 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2080624 Title: Remove from oracular, EOL upstream Status in fabric-manager-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Bug description: This driver is EOL now, so it should be removed from oracular. https://endoflife.date/nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/2080624/+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 2080624] [NEW] Remove from oracular, EOL upstream
Public bug reported: This driver is EOL now, so it should be removed from oracular. https://endoflife.date/nvidia ** Affects: fabric-manager-470 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: nvidia-graphics-drivers-470-server (Ubuntu) Importance: Undecided Status: Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2080624 Title: Remove from oracular, EOL upstream Status in fabric-manager-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-470-server package in Ubuntu: Fix Released Bug description: This driver is EOL now, so it should be removed from oracular. https://endoflife.date/nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/2080624/+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 2080624] Re: Remove from oracular, EOL upstream
Removing packages from oracular: nvidia-graphics-drivers-470-server 470.256.02-0ubuntu2 in oracular libnvidia-cfg1-460-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-cfg1-470-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-common-460-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-common-460-server 470.256.02-0ubuntu2 in oracular arm64 libnvidia-common-460-server 470.256.02-0ubuntu2 in oracular armhf libnvidia-common-460-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-common-460-server 470.256.02-0ubuntu2 in oracular ppc64el libnvidia-common-460-server 470.256.02-0ubuntu2 in oracular riscv64 libnvidia-common-460-server 470.256.02-0ubuntu2 in oracular s390x libnvidia-common-470-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-common-470-server 470.256.02-0ubuntu2 in oracular arm64 libnvidia-common-470-server 470.256.02-0ubuntu2 in oracular armhf libnvidia-common-470-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-common-470-server 470.256.02-0ubuntu2 in oracular ppc64el libnvidia-common-470-server 470.256.02-0ubuntu2 in oracular riscv64 libnvidia-common-470-server 470.256.02-0ubuntu2 in oracular s390x libnvidia-compute-460-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-compute-460-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-compute-470-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-compute-470-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-decode-460-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-decode-460-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-decode-470-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-decode-470-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-encode-460-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-encode-460-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-encode-470-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-encode-470-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-extra-460-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-extra-460-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-extra-470-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-extra-470-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-fbc1-460-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-fbc1-460-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-fbc1-470-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-fbc1-470-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-gl-460-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-gl-460-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-gl-470-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-gl-470-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-ifr1-460-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-ifr1-460-server 470.256.02-0ubuntu2 in oracular i386 libnvidia-ifr1-470-server 470.256.02-0ubuntu2 in oracular amd64 libnvidia-ifr1-470-server 470.256.02-0ubuntu2 in oracular i386 nvidia-compute-utils-460-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-compute-utils-470-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-dkms-460-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-dkms-470-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-driver-460-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-driver-470-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-headless-460-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-headless-470-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-headless-no-dkms-460-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-headless-no-dkms-470-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-kernel-common-460-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-kernel-common-470-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-kernel-source-460-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-kernel-source-470-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-utils-460-server 470.256.02-0ubuntu2 in oracular amd64 nvidia-utils-470-server 470.256.02-0u
[Kernel-packages] [Bug 2073108] Please test proposed package
Hello 何思亮, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.34 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2073108 Title: Failed to detect Wireless LAN device Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2073108 [Impact] ath10k loaded firmware ath10k/QCA6174/hw3.0 with error [Fix] Update FW binary to the latest for ath10k/QCA6174/hw3.0 [Test Case] 1. Install 5.15.0-116.126-generic kernel with ath10k driver enabled. 2. Install the linux-firmware with latest ath10k/QCA6174/hw3.0 firmware 3. Run checkbox test case com.canonical.certification::wireless/detect. [Where problems could occur] New firmware is only loaded by the QCA6174 with hw 3.0, we haven't tested the device with hw 2.0. --- udev failed to detect wireless LAN at 5.15.0-116.126-generic. It was passed at 5.15.0-115.125-generic. terminal log: ubuntu@dell-precision-5530-c26342:~$ nmcli device status DEVICE TYPE STATE CONNECTION enx00e04c68fef9 ethernet connected netplan-enx00e04c68fef9 lo loopback unmanaged -- ubuntu@dell-precision-5530-c26342:~$ iw dev ubuntu@dell-precision-5530-c26342:~$ ls /sys/class/net | grep wl ubuntu@dell-precision-5530-c26342:~$ checkbox log: ---[ Detect if at least one Wireless LAN device is detected ]--- ID: com.canonical.certification::wireless/detect Category: Wireless networking tests No devices detected by udev Outcome: job failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-116-generic 5.15.0-116.126 ProcVersionSignature: Ubuntu 5.15.0-116.126-generic 5.15.158 Uname: Linux 5.15.0-116-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1108 F pulseaudio CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/) CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Mon Jul 15 05:45:08 2024 InstallationDate: Installed on 2022-05-10 (796 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enx00e04c68fef9 no wireless extensions. MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-116-generic root=UUID=8390b3ba-ff2e-4b3f-9828-f7e201e8c536 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-116-generic N/A linux-backports-modules-5.15.0-116-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.31 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This
[Kernel-packages] [Bug 2079024] Please test proposed package
Hello En-Wei, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.34 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2079024 Title: Update mt7925 BT FW to avoid bluetooth_obex_send failed Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Committed Bug description: [Impact] In OEM project, we found that the Mediatek mtk7925 bluetooth device will fail on transmitting files with the peer device by OBEX. The bluetooth mouse, keyboard and headset are working while this happen. [Fix] Cherry-pick the mediatek/mt7925/BT_RAM_CODE_MT7925_1_1_hdr.bin from the linux-firmware:Oracular: https://kernel.ubuntu.com/gitea/kernel/linux- firmware/commit/79c19bb0cda0abc97fdca49d3165f3b419aa2ac6 [Test Plan] 1. Boot into OS 2. checkbox-cli run com.canonical.certification::bluetooth/bluetooth_obex_send [Where problems could occur] May cause regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2079024/+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 2073047] Please test proposed package
Hello Eugene, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.34 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2073047 Title: Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops working after a few suspend/resume cycles Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: SRU Justification: == [Impact] AX200 Bluetooth stops working after a few suspend/resume cycles. [Fix] Update the Bluetooth firmware and align with upstream. [Test] Bug reporter tested on hardware, Bluetooth works fine. [Where problems could occur] It may break Bluetooth of AX200. === After upgrading to Linux 6.8.0-38, Bluetooth adapter (USB part of the Intel AX200) stops working after a few suspend/resume cycles. WiFi (PCIe part) continues to work as expected. Kernel log shows: Bluetooth: hci0: Reading Intel version command failed (-110) instead of the usual: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 Bluetooth: hci0: Device revision is 1 Bluetooth: hci0: Secure boot is enabled Bluetooth: hci0: OTP lock is enabled Bluetooth: hci0: API lock is enabled Bluetooth: hci0: Debug lock is disabled Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi Bluetooth: hci0: Boot Address: 0x24800 Bluetooth: hci0: Firmware Version: 255-255.255 Bluetooth: hci0: Waiting for firmware download to complete Bluetooth: hci0: Firmware loaded in 2111457 usecs Bluetooth: hci0: Waiting for device to boot Bluetooth: hci0: Device booted in 14560 usecs Bluetooth: hci0: Malformed MSFT vendor event: 0x02 Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc Bluetooth: hci0: Applying Intel DDC parameters completed Bluetooth: hci0: Firmware revision 0.3 build 249 week 27 2023 Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported. Bluetooth: MGMT ver 1.22 First appeared on 6.8.0-38, 6.8.0-36 and earlier worked without issues. I suspect linux-firmware might be missing updates corresponding to changes in the kernel driver or a regression was introduced in the update. Machine: Dell XPS13-9350 Device: Intel AX200 Rev 1a (WiFi/Bluetooth combo) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2073047/+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 2073525] Please test proposed package
Hello Thibf, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.34 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2073525 Title: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids Status in The Kobuk project: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: Public bug of https://bugs.launchpad.net/bugs/2073432 [ Impact ] The QAT kernel driver require those for For Sierra forest and Granite rapids hardware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx_mmp.bin [ Test Plan ] cpa_sample_code supplied with qatlib and the Linux kernel can be run to validate the firmware. [ Where problems could occur ] QAT not working on those platform. [ Other Info ] * Requested by intel, compatible on kernel since 6.4, mantic doesn't apply as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/kobuk/+bug/2073525/+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 2076180] Please test proposed package
Hello Juerg, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.34 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2076180 Title: Add new firmwares for 6.8 hwe kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] The 6.8 HWE kernel requires firmware that is not (yet) provided by linux-firmware in Jammy. This obviously results in non-functional HW components. [Fix] Add missing firmware blobs and links. [Test Case] Ideally: Verify that the 6.8 kernel loads the new firmware blobs and the affected HW components function as expected. Realistically: Mostly untestable due to lack of availability of relevant HW. [Where Problems Could Occur] This adds only new firmware blobs (and symbolic links) that the 5.15 GA kernel doesn't care about so should not introduce any issues. In case that's an incorrect assumption, some HW components might not function properly if the new blobs are incompatible with the 5.15 GA kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2076180/+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 2077296] Please test proposed package
Hello AaronMa, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.34 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2077296 Title: Add more region support of QCOM WiFi WCN7850 Status in HWE Next: Fix Committed Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Released Status in linux-firmware source package in Oracular: Fix Committed Bug description: [Impact] Qualcomm WiFi chip WCN7850 needs new board-2.bin for more regions. [Fix] Update board-2.bin in linux-firmware. [Test] Boot up, and WiFi works fine. [Where problems could occur] It may break Qualcomm WiFi WCN7850. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2077296/+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 2077490] Please test proposed package
Hello Kevin, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.34 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2077490 Title: Error: out of memory while booting after installing the linux-firmware in proposed Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] I found that there are some machines in cert lab can't boot after installing the linux-frimware in proposed with 6.8.0-40 kernel. After selecting booting with the 6.8.0-40 kernel, it shows error: out of memory on the screen then freeze. There aren't any journal logs available, since they froze at very early stage. Following are the machines got impacted for now https://certification.canonical.com/hardware/202306-31695/ https://certification.canonical.com/hardware/202306-31696/ Problem details: The linux-firmware package provides new (gigantic) firmware blobs and symlinks to directories that contain those. initramfs-tools can't handle the directory symlinks and puts multiple copies of the same blobs into the initrd blowing it up to a size where it becomes problematic on some machines. [Test Case] Verify the affected machine boots again with the updated firmware package. Install updated linux-firmware package and confirm that there are no duplicate firmware files in /lib/firmware and inside the initrd. Also verify that there are no broken symlinks. [Where Problems Could Occur] If the new symlinks are broken, we end up with drivers not finding their firmwares which results in non-functional HW components. [Notes] This is not a general solution for the problem of the ever growing size of the initrd. It just alleviate it some. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2077490/+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 2080428] Please test proposed package
Hello Maximilian, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.34 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2080428 Title: Updating firmware disabled QCOM WiFi WCN7850 on T14 Gen5 AMD Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Committed Status in linux-firmware source package in Oracular: Fix Committed Bug description: [Impact] After installing new package updates as suggested by ubuntu, my WiFi Card (Qualcomm WCN785x Wi-Fi 7(802.11be) as far as lshw -C network is concerned) did not connect to the network again after waking the laptop from idle. After some research I found this bug report: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2077296 It seems that after updating the firmware package after the bugfix for the mentioned bug got released, the updated file board-2.bin is now broken for at least T14 Gen5 AMD. In the mentioned bugfix thread, a person already posted this issue yesterday. However, I am reposting it here as suggested by Timo in https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/2077296/comments/5. Running sudo dmesg | grep ath12k reveals that the board data could not be fetched from the updated file: [2.381547] ath12k_pci :02:00.0: BAR 0 [mem 0x9060-0x907f 64bit]: assigned [2.381567] ath12k_pci :02:00.0: enabling device ( -> 0002) [2.382640] ath12k_pci :02:00.0: MSI vectors: 16 [2.382647] ath12k_pci :02:00.0: Hardware name: wcn7850 hw2.0 [3.479946] ath12k_pci :02:00.0: chip_id 0x2 chip_family 0x4 board_id 0xff soc_id 0x40170200 [3.479950] ath12k_pci :02:00.0: fw_version 0x100301e1 fw_build_timestamp 2023-12-06 04:05 fw_build_id QC_IMAGE_VERSION_STRING=WLAN.HMT.1.0.c5-00481-QCAHMTSWPL_V1.0_V2.0_SILICONZ-3 [3.492086] ath12k_pci :02:00.0: failed to fetch board data for bus=pci,vendor=17cb,device=1107,subsystem-vendor=17aa,subsystem-device=e0e6,qmi-chip-id=2,qmi-board-id=255 from ath12k/WCN7850/hw2.0/board-2.bin [3.492101] ath12k_pci :02:00.0: failed to fetch board.bin from WCN7850/hw2.0 [3.492103] ath12k_pci :02:00.0: qmi failed to load bdf: [3.492105] ath12k_pci :02:00.0: qmi failed to load board data file:-2 Any help is greatly appreciated. [Fix] Revert offending commit. [Where Problems Could Occur] Limited to ath12k wifi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2080428/+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 2080529] Re: oracular/linux-gke and oracular/linux-ibm removal
Removing packages from oracular: linux-gke 6.8.0-1003.5 in oracular linux-buildinfo-6.8.0-1003-gke 6.8.0-1003.5 in oracular amd64 linux-buildinfo-6.8.0-1003-gke 6.8.0-1003.5 in oracular arm64 linux-gke-headers-6.8.0-1003 6.8.0-1003.5 in oracular amd64 linux-gke-headers-6.8.0-1003 6.8.0-1003.5 in oracular arm64 linux-gke-tools-6.8.0-1003 6.8.0-1003.5 in oracular amd64 linux-gke-tools-6.8.0-1003 6.8.0-1003.5 in oracular arm64 linux-headers-6.8.0-1003-gke 6.8.0-1003.5 in oracular amd64 linux-headers-6.8.0-1003-gke 6.8.0-1003.5 in oracular arm64 linux-image-unsigned-6.8.0-1003-gke 6.8.0-1003.5 in oracular amd64 linux-image-unsigned-6.8.0-1003-gke 6.8.0-1003.5 in oracular arm64 linux-modules-6.8.0-1003-gke 6.8.0-1003.5 in oracular amd64 linux-modules-6.8.0-1003-gke 6.8.0-1003.5 in oracular arm64 linux-modules-extra-6.8.0-1003-gke 6.8.0-1003.5 in oracular amd64 linux-modules-extra-6.8.0-1003-gke 6.8.0-1003.5 in oracular arm64 linux-tools-6.8.0-1003-gke 6.8.0-1003.5 in oracular amd64 linux-tools-6.8.0-1003-gke 6.8.0-1003.5 in oracular arm64 linux-meta-gke 6.8.0-1003.5 in oracular linux-gke 6.8.0-1003.5 in oracular amd64 linux-gke 6.8.0-1003.5 in oracular arm64 linux-headers-gke 6.8.0-1003.5 in oracular amd64 linux-headers-gke 6.8.0-1003.5 in oracular arm64 linux-image-gke 6.8.0-1003.5 in oracular amd64 linux-image-gke 6.8.0-1003.5 in oracular arm64 linux-tools-gke 6.8.0-1003.5 in oracular amd64 linux-tools-gke 6.8.0-1003.5 in oracular arm64 linux-signed-gke 6.8.0-1003.5 in oracular linux-image-6.8.0-1003-gke 6.8.0-1003.5 in oracular amd64 linux-image-6.8.0-1003-gke 6.8.0-1003.5 in oracular arm64 Comment: lp#2080529 Remove [y|N]? y 3 packages successfully removed. ** Changed in: linux-gke (Ubuntu Oracular) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2080529 Title: oracular/linux-gke and oracular/linux-ibm removal Status in linux-gke package in Ubuntu: Fix Released Status in linux-ibm package in Ubuntu: Fix Released Status in linux-gke source package in Oracular: Fix Released Status in linux-ibm source package in Oracular: Fix Released Bug description: During Oracular archive opening, noble/linux-ibm and noble/linux-gke were forward copied but these kernels are EOL and not supported in OO, thus asking for archive removal of these two packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2080529/+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 2080529] Re: oracular/linux-gke and oracular/linux-ibm removal
Removing packages from oracular: linux-ibm 6.8.0-1005.5 in oracular linux-buildinfo-6.8.0-1005-ibm 6.8.0-1005.5 in oracular amd64 linux-headers-6.8.0-1005-ibm 6.8.0-1005.5 in oracular amd64 linux-ibm-cloud-tools-common 6.8.0-1005.5 in oracular amd64 linux-ibm-cloud-tools-common 6.8.0-1005.5 in oracular arm64 linux-ibm-cloud-tools-common 6.8.0-1005.5 in oracular armhf linux-ibm-cloud-tools-common 6.8.0-1005.5 in oracular i386 linux-ibm-cloud-tools-common 6.8.0-1005.5 in oracular ppc64el linux-ibm-cloud-tools-common 6.8.0-1005.5 in oracular riscv64 linux-ibm-cloud-tools-common 6.8.0-1005.5 in oracular s390x linux-ibm-headers-6.8.0-1005 6.8.0-1005.5 in oracular amd64 linux-ibm-headers-6.8.0-1005 6.8.0-1005.5 in oracular arm64 linux-ibm-headers-6.8.0-1005 6.8.0-1005.5 in oracular armhf linux-ibm-headers-6.8.0-1005 6.8.0-1005.5 in oracular i386 linux-ibm-headers-6.8.0-1005 6.8.0-1005.5 in oracular ppc64el linux-ibm-headers-6.8.0-1005 6.8.0-1005.5 in oracular riscv64 linux-ibm-headers-6.8.0-1005 6.8.0-1005.5 in oracular s390x linux-ibm-source-6.8.0 6.8.0-1005.5 in oracular amd64 linux-ibm-source-6.8.0 6.8.0-1005.5 in oracular arm64 linux-ibm-source-6.8.0 6.8.0-1005.5 in oracular armhf linux-ibm-source-6.8.0 6.8.0-1005.5 in oracular i386 linux-ibm-source-6.8.0 6.8.0-1005.5 in oracular ppc64el linux-ibm-source-6.8.0 6.8.0-1005.5 in oracular riscv64 linux-ibm-source-6.8.0 6.8.0-1005.5 in oracular s390x linux-ibm-tools-6.8.0-1005 6.8.0-1005.5 in oracular amd64 linux-ibm-tools-common 6.8.0-1005.5 in oracular amd64 linux-ibm-tools-common 6.8.0-1005.5 in oracular arm64 linux-ibm-tools-common 6.8.0-1005.5 in oracular armhf linux-ibm-tools-common 6.8.0-1005.5 in oracular i386 linux-ibm-tools-common 6.8.0-1005.5 in oracular ppc64el linux-ibm-tools-common 6.8.0-1005.5 in oracular riscv64 linux-ibm-tools-common 6.8.0-1005.5 in oracular s390x linux-image-unsigned-6.8.0-1005-ibm 6.8.0-1005.5 in oracular amd64 linux-modules-6.8.0-1005-ibm 6.8.0-1005.5 in oracular amd64 linux-modules-extra-6.8.0-1005-ibm 6.8.0-1005.5 in oracular amd64 linux-modules-iwlwifi-6.8.0-1005-ibm 6.8.0-1005.5 in oracular amd64 linux-tools-6.8.0-1005-ibm 6.8.0-1005.5 in oracular amd64 linux-meta-ibm 6.8.0-1005.5 in oracular linux-headers-ibm 6.8.0-1005.5 in oracular amd64 linux-headers-ibm-classic 6.8.0-1005.5 in oracular amd64 linux-headers-ibm-lts-24.04 6.8.0-1005.5 in oracular amd64 linux-ibm 6.8.0-1005.5 in oracular amd64 linux-ibm-classic 6.8.0-1005.5 in oracular amd64 linux-ibm-lts-24.04 6.8.0-1005.5 in oracular amd64 linux-image-ibm 6.8.0-1005.5 in oracular amd64 linux-image-ibm-classic 6.8.0-1005.5 in oracular amd64 linux-image-ibm-lts-24.04 6.8.0-1005.5 in oracular amd64 linux-modules-iwlwifi-ibm 6.8.0-1005.5 in oracular amd64 linux-modules-iwlwifi-ibm-classic 6.8.0-1005.5 in oracular amd64 linux-modules-iwlwifi-ibm-lts-24.04 6.8.0-1005.5 in oracular amd64 linux-tools-ibm 6.8.0-1005.5 in oracular amd64 linux-tools-ibm-classic 6.8.0-1005.5 in oracular amd64 linux-tools-ibm-lts-24.04 6.8.0-1005.5 in oracular amd64 linux-signed-ibm 6.8.0-1005.5 in oracular linux-image-6.8.0-1005-ibm 6.8.0-1005.5 in oracular amd64 Comment: lp#2080529 Remove [y|N]? y 3 packages successfully removed. ** Changed in: linux-ibm (Ubuntu Oracular) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gke in Ubuntu. https://bugs.launchpad.net/bugs/2080529 Title: oracular/linux-gke and oracular/linux-ibm removal Status in linux-gke package in Ubuntu: Fix Released Status in linux-ibm package in Ubuntu: Fix Released Status in linux-gke source package in Oracular: Fix Released Status in linux-ibm source package in Oracular: Fix Released Bug description: During Oracular archive opening, noble/linux-ibm and noble/linux-gke were forward copied but these kernels are EOL and not supported in OO, thus asking for archive removal of these two packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gke/+bug/2080529/+subscriptions -- Mailing list: https://launchpad.net/~kernel-pa
[Kernel-packages] [Bug 2080495] Re: A lot of NIC driver error messages appear when powering off the machine.
** Package changed: linux-signed-hwe-6.8 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2080495 Title: A lot of NIC driver error messages appear when powering off the machine. Status in linux package in Ubuntu: New Bug description: [Summary] During the SRU testing, I found a Lenovo workstation has multiple NICs installed that failed to wake up from cold-reboot by rtc event. After some investigations, I found that it's because too many kernel message appear and slow down the power off. We don't have any connection on those impacted NIC, so we still can access the machine, but I assume it should also be a regression for 6.8 kerenl. Those error messages didn't be recorded by journalctl, so I just took a photo and converted them to text. [Expected result] SRU test can continue after cold-reboot [Actual result] Cold-reboot takes too long to power off that exceed the wake up time we set for rtc. [Additional information] Following are the DUTs that are impacted. https://certification.canonical.com/hardware/202310-32275/ ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.8.0-44-generic 6.8.0-44.44~22.04.1 ProcVersionSignature: Ubuntu 6.8.0-44.44~22.04.1-generic 6.8.12 Uname: Linux 6.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.6 Architecture: amd64 CasperMD5CheckMismatches: ./preseed/project.cfg CasperMD5CheckResult: fail Date: Thu Sep 12 16:44:46 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-jammy-amd64-20240129-711 InstallationDate: Installed on 2024-09-11 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - pc-sutton-jammy-amd64-20240129-711 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080495/+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 2080418] Re: package linux-firmware 1.187.39 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1
Setting up linux-firmware (1.187.39) ... update-initramfs: Generating /boot/initrd.img-4.15.0-213-generic W: initramfs-tools configuration sets RESUME=UUID=a994e29c-6268-41db-9445-8a6ef0cd7f67 W: but no matching swap device is available. Warning: /dev/disk/by-id/ata-SanDisk_SDSSDA240G_171981463015 is not on the first disk Fatal: open /boot/vmlinuz-4.4.0-101-generic: No such file or directory run-parts: /etc/initramfs/post-update.d//runlilo exited with return code 1 dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 -- 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/2080418 Title: package linux-firmware 1.187.39 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: New Bug description: I tried to upgrade during upgrade several mistakes occurred. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.39 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: peter 1925 F pulseaudio /dev/snd/controlC0: peter 1925 F pulseaudio /dev/snd/controlC1: peter 1925 F pulseaudio CasperMD5CheckResult: skip Date: Wed Sep 11 18:29:13 2024 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=a994e29c-6268-41db-9445-8a6ef0cd7f67 InstallationDate: Installed on 2016-08-16 (2948 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: LENOVO INVALID PackageArchitecture: all ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic root=UUID=f9a6c7f3-1695-4bb6-9272-620cc2bc2c63 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26.17 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.187.39 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2024-09-11 (0 days ago) dmi.bios.date: 05/16/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 9HKT41AUS dmi.board.vendor: LENOVO dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9HKT41AUS:bd05/16/2011:svnLENOVO:pnINVALID:pvrLenovoProduct:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: INVALID dmi.product.version: Lenovo Product dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2080418/+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 2080322] Re: [SRU] Disable CONFIG_TCG_TPM2_HMAC to avoid performance loss after v6.10
** 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/2080322 Title: [SRU] Disable CONFIG_TCG_TPM2_HMAC to avoid performance loss after v6.10 Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.11 source package in Noble: In Progress Status in linux source package in Oracular: Fix Committed Status in linux-oem-6.11 source package in Oracular: Invalid Bug description: [Impact] significant delays at bootup, the bootup time is 7 sec when this feature is disabled, but 20 sec when it's enabled. [Fix] v6.10-rc1 introduce encryption overhead to all kernel to TPM transactions, Disable it by default until there is a real fix. [Test] Tested on hardware, bootup is 7 sec as 6.8 noble kernel. [Where problems could occur] It may less security or break TPM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080322/+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 2069993] Re: Panels show garbage or flickering when i915.psr2 enabled
** Changed in: linux-oem-6.11 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2069993 Title: Panels show garbage or flickering when i915.psr2 enabled Status in linux package in Ubuntu: New Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Committed Status in linux-oem-6.11 source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: SRU verification for oem-6.8-noble: [Impact] In https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2046315, we've cherry-picked the 8 patches from the most recent mainline kernel to oem-6.8 to fix the panel flickering problem in the Dell OEM project. However, OEM reports that the patches have regression on 6.8.0-1006-oem. For now, we apply the workaround patches from oem-6.5 to fix the bug. In the meantime, we've reported the issue to Intel and are waiting for the fix. Once the fix is available in the mainline kernel, we'll backport the fix into oem-6.8 kernel and revert the workaround patches, as well as submit them to Oracular. Upstream bug: https://gitlab.freedesktop.org/drm/intel/-/issues/9739 Upstream patch submission: https://patchwork.freedesktop.org/series/137524/ [Fix] Apply workaround patches from oem-6.5 to oem-6.8 *** Update *** For oem-6.11, cherry-pick two upstream fixes currently in linux-next: a13494de5325 drm/i915/display: Increase Fast Wake Sync length as a quirk 43cf50eb1408 drm/i915/display: Add mechanism to use sink model when applying quirk [Test Plan] The machines mentioned in the attachment (containing the problematic panel's EDID) would have flickering graphics with the linux-6.8.0-1006-oem kernel. The flickering graphic is gone after applying the workaround patches. [Where problems could occur] The workaround patches add some quirks that disable PSR2 on some panels. So far, there are 7 panels listed in the quirks (other panels used by OEM products are flickering-free without the patches). If OEM starts using other panels in the future, it's not sure that the panels will be flickering-free. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069993/+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 2080190] Re: Soundwire support for Dell SKU0CDC devices
** Changed in: linux-oem-6.11 (Ubuntu Oracular)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2080190
Title:
Soundwire support for Dell SKU0CDC devices
Status in linux package in Ubuntu:
New
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.11 source package in Noble:
New
Status in linux source package in Oracular:
New
Status in linux-oem-6.11 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing soundwire support for Dell SKU0CDC deivces.
[Fix]
The upstream fix 9307694f340e ("ASoC: Intel: sof_sdw: Add quirks from some
new Dell laptops") and its dependency are required.
[Test Case]
1. Install linux-firmware proposed in
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2077829
2. Install the firmware-sof w/ sof-lnl-cs42l43-l0.tplg
3. Test audio functions on Taroko LNL platforms.
[Where problems could occur]
New devices, may need further polishments.
== original bug description ==
Sep 05 04:57:35 localhost kernel: sof-audio-pci-intel-lnl :00:1f.3:
Topology: ABI 3:29:0 Kernel ABI 3:23:0
Sep 05 04:57:35 localhost kernel: sof-audio-pci-intel-lnl :00:1f.3:
error: can't connect DAI alh-copier.Playback-SmartAmp.0 stream Playback-SmartAmp
Sep 05 04:57:35 localhost kernel: sof-audio-pci-intel-lnl :00:1f.3:
failed to add widget type 27 name : alh-copier.Playback-SmartAmp.0 stream
Playback-SmartAmp
Sep 05 04:57:35 localhost kernel: sof_sdw sof_sdw: ASoC: failed to load
widget alh-copier.Playback-SmartAmp.0
Sep 05 04:57:35 localhost kernel: sof_sdw sof_sdw: ASoC: topology: could not
load header: -22
Sep 05 04:57:35 localhost kernel: sof-audio-pci-intel-lnl :00:1f.3:
error: tplg component load failed -22
Sep 05 04:57:35 localhost kernel: sof-audio-pci-intel-lnl :00:1f.3:
error: failed to load DSP topology -22
Sep 05 04:57:35 localhost kernel: sof-audio-pci-intel-lnl :00:1f.3: ASoC:
error at snd_soc_component_probe on :00:1f.3: -22
Sep 05 04:57:35 localhost kernel: sof_sdw sof_sdw: ASoC: failed to
instantiate card -22
Sep 05 04:57:35 localhost kernel: sof_sdw sof_sdw: error -EINVAL:
snd_soc_register_card failed -22
Sep 05 04:57:35 localhost kernel: sof_sdw sof_sdw: probe with driver sof_sdw
failed with error -22
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080190/+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 2071821] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2071821 Title: Support Intel IPU7 MIPI camera Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.11 package in Ubuntu: Invalid Status in usbio-drivers package in Ubuntu: Fix Released Status in linux source package in Noble: Invalid Status in linux-firmware source package in Noble: Fix Released Status in linux-oem-6.11 source package in Noble: New Status in usbio-drivers source package in Noble: Won't Fix Status in linux source package in Oracular: New Status in linux-firmware source package in Oracular: Fix Released Status in linux-oem-6.11 source package in Oracular: Invalid Status in usbio-drivers source package in Oracular: Fix Released Bug description: [SRU Justification] [Impact] Missing ipu7 firmware for Intel IPU7 MIPI camera platforms. [Fix] https://github.com/intel/ipu7-camera- bins/commit/398589deb5f8e7d16d13f0e12f0b49977f464594 [Test Case] With a working driver and the firmware in position, there should be messages in dmesg output: ``` kernel: intel-ipu7 intel-ipu7: cpd file name: intel/ipu/ipu7_fw.bin kernel: intel-ipu7 intel-ipu7: FW binary0 info: kernel: intel-ipu7 intel-ipu7: Name: psys kernel: intel-ipu7 intel-ipu7: Version: 1.1.9.240627135220 kernel: intel-ipu7 intel-ipu7: Timestamp: build_id:331942702 kernel: intel-ipu7 intel-ipu7: Commit: commit_id:d84f5c35 kernel: intel-ipu7 intel-ipu7: FW binary1 info: kernel: intel-ipu7 intel-ipu7: Name: isys kernel: intel-ipu7 intel-ipu7: Version: 1.1.9.240627135318 kernel: intel-ipu7 intel-ipu7: Timestamp: build_id:3823931988 kernel: intel-ipu7 intel-ipu7: Commit: commit_id:d84f5c35 ``` [Where problems could occur] New hardware. No know issue yet. [Other Info] This is the firmware part only, and the whole framework has to be enabled with both firmware, kernel driver and userspace HAL. Nominate for Noble and Oracular. == original bug report = Kernel drivers: * https://github.com/intel/ipu7-drivers * https://github.com/intel/vision-drivers * https://github.com/intel/usbio-drivers Kernel tree patch: * https://github.com/intel/ivsc-driver/commit/47e7c4a446c8ea8c741ff5a32fa7b19f9e6fd47e linux-firmware: * https://github.com/intel/ipu7-camera-bins Userspace frameworks: * To be discussed. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:ubuntu 1247 F pipewire CRDA: N/A CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs ./boot/grub/grub.cfg CasperMD5CheckResult: fail Dependencies: firmware-sof-signed 2023.12.1-1ubuntu1+exp.5 [origin: unknown] DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04b-edge-20240821-70 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-08-22 (4 days ago) InstallationMedia: Ubuntu OEM 24.04 LTS "Noble Numbat" - Release amd64 (20240820) IwConfig: lono wireless extensions. enx00e04c6801fa no wireless extensions. MachineType: Dell Inc. XPS 13 9350 Package: linux-firmware PackageArchitecture: amd64 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-1002-oem root=UUID=ef38ac81-5316-4558-aa9d-91eb7efb1ce9 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.11.0-1002.2-oem 6.11.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.11.0-1002-oem N/A linux-backports-modules-6.11.0-1002-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: noble package-from-proposed third-party-packages Uname: Linux 6.11.0-1002-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 08/01/2024 dmi.bios.release: 1.0 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 024653 dmi.board.vendor: D
[Kernel-packages] [Bug 2077296] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2077296 Title: Add more region support of QCOM WiFi WCN7850 Status in HWE Next: Fix Committed Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Released Status in linux-firmware source package in Oracular: Fix Committed Bug description: [Impact] Qualcomm WiFi chip WCN7850 needs new board-2.bin for more regions. [Fix] Update board-2.bin in linux-firmware. [Test] Boot up, and WiFi works fine. [Where problems could occur] It may break Qualcomm WiFi WCN7850. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2077296/+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 2073525] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2073525 Title: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids Status in The Kobuk project: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: Public bug of https://bugs.launchpad.net/bugs/2073432 [ Impact ] The QAT kernel driver require those for For Sierra forest and Granite rapids hardware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx_mmp.bin [ Test Plan ] cpa_sample_code supplied with qatlib and the Linux kernel can be run to validate the firmware. [ Where problems could occur ] QAT not working on those platform. [ Other Info ] * Requested by intel, compatible on kernel since 6.4, mantic doesn't apply as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/kobuk/+bug/2073525/+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 2077112] Update Released
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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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/2077112
Title:
Missing Huc/Gsc support for Intel GFX Xe driver for Lunar Lake
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Status in linux-firmware source package in Oracular:
Fix Released
Bug description:
[Impact]
Missing Huc/Gsc firmware for Intel GFX Xe driver for Lunar Lake.
[Fix]
Few commits from upstream tag intel-2024-08-02.
[Test Case]
In dmesg:
```
xe :00:02.0: [drm] Found LUNARLAKE (device ID 64a0) display version 20.00
xe :00:02.0: [drm] Using GuC firmware from xe/lnl_guc_70.bin version
70.29.2
xe :00:02.0: [drm] Using GuC firmware from xe/lnl_guc_70.bin version
70.29.2
xe :00:02.0: [drm] Using HuC firmware from xe/lnl_huc.bin version 9.4.13
xe :00:02.0: [drm] Using GSC firmware from xe/lnl_gsc_1.bin version
104.0.0.1161
```
[Where problems could occur]
There has been one Xe fw at intel/lnl_guc_70.bin, and the other Xe
binaries are to complete Xe driver support on Lunar Lake. No known
issue so far.
[Other Info]
For Oracular, it has been included in version
20240808.gite131a437-0ubuntu1, leaving Noble as the only target of the
nomination for OEM-6.11.
== original bug report ==
* Kernel
-
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=e814902866ed22bc07d2af1303f3183357a438e8
("drm/xe/huc: Define HuC binary for LNL")
-
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=f4aa02c43969c36213a7fd4e56831693fc83ec4b
("drm/xe/gsc: Define GSC binary for LNL")
-
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=4eb0aab6e4434ada240286d934651dfdb2e08301
("drm/xe/guc: Bump minimum required GuC version to v70.29.2")
* linux-firmware
-
https://lore.kernel.org/linux-firmware/20240802175932.784781-1-daniele.ceraolospu...@intel.com/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2077112/+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 2077509] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2077509 Title: Missing firmware for Intel(R) Wi-Fi 7 BE200 320MHz Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Noble: Fix Released Status in linux-firmware source package in Oracular: Fix Released Bug description: [SRU Justification] [Impact] Missing iwlwifi for Intel BE200. ``` $ sudo dmesg|grep iwlwifi [ 3.274505] iwlwifi :82:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz [ 3.275097] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-92.ucode failed with error -2 [ 3.275115] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-91.ucode failed with error -2 [ 3.275128] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-90.ucode failed with error -2 [ 3.275129] iwlwifi :82:00.0: no suitable firmware found! [ 3.275131] iwlwifi :82:00.0: minimum version required: iwlwifi-gl-c0-fm-c0-90 [ 3.275132] iwlwifi :82:00.0: maximum version supported: iwlwifi-gl-c0-fm-c0-92 [ 3.275133] iwlwifi :82:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git ``` [Fix] Two upstream linux-firmware commits from upstream tag iwlwifi- fw-2024-07-23 fulfills the need. [Test Case] Expecting similar dmesg: ``` $ sudo dmesg|grep iwlwifi [ 2.548446] iwlwifi :82:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz [ 2.555076] iwlwifi :82:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.182.4.1 [ 2.07] iwlwifi :82:00.0: loaded firmware version 92.67ce4588.0 gl-c0-fm-c0-92.ucode op_mode iwlmvm [ 3.017113] iwlwifi :82:00.0: WRT: Invalid buffer destination [ 3.281636] iwlwifi :82:00.0: loaded PNVM version da3b5cf2 [ 3.302582] iwlwifi :82:00.0: Detected RF FM, rfid=0x112200 [ 3.402403] iwlwifi :82:00.0: base HW address: a0:02:a5:79:66:d4 [ 3.570939] iwlwifi :82:00.0 wlp130s0f0: renamed from wlan0 ``` [Where problems could occur] In kernels >= v6.11-rc1, the supported UCODE API range is [90, 92], and for v6.10 kernels [80, 90], v6.9 [80, 89], v6.8 [80, 86]. So this affects kernel >= 6.10, and for them BE200 is not supported yet. [Other Info] This affects kernel >= 6.10, and therefore Noble and Oracular should be in the list. While linux-firmware/oracular has included iwlwifi- fw-2024-07-23, it makes Noble the only one nominated for fixing. == original bug report == Got: $ sudo dmesg|grep iwlwifi [3.257466] iwlwifi :82:00.0: enabling device ( -> 0002) [3.274366] iwlwifi :82:00.0: Detected crf-id 0x2001910, cnv-id 0x2001910 wfpm id 0x8000 [3.274502] iwlwifi :82:00.0: PCI dev 272b/40f0, rev=0x472, rfid=0x112200 [3.274505] iwlwifi :82:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz [3.275097] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-92.ucode failed with error -2 [3.275115] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-91.ucode failed with error -2 [3.275128] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-90.ucode failed with error -2 [3.275129] iwlwifi :82:00.0: no suitable firmware found! [3.275131] iwlwifi :82:00.0: minimum version required: iwlwifi-gl-c0-fm-c0-90 [3.275132] iwlwifi :82:00.0: maximum version supported: iwlwifi-gl-c0-fm-c0-92 [3.275133] iwlwifi :82:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Expecting: $ sudo dmesg|grep iwlwifi [2.541369] iwlwifi :82:00.0: enabling device ( -> 0002) [2.548367] iwlwifi :82:00.0: Detected crf-id 0x2001910, cnv-id 0x2001910 wfpm id 0x8000 [2.548444] iwlwifi :82:00.0: PCI dev 272b/40f0, rev=0x472, rfid=0x112200 [2.548446] iwlwifi :82:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz [2.555076] iwlwifi :82:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.182.4.1 [2.07] iwlwifi :82:00.0: loaded firmware version 92.67ce4588.0 gl-c0-fm-c0-92.ucode op_mode iwlmvm [3.017113] iwlwifi :82:00.0: WRT: Invalid buffer destination [3.281636] iwlwifi :82:00.0: loaded PNVM version da3b5cf2 [3.302582] iwlwifi :82:00.0: Detected RF FM, rfid=0x112200 [
[Kernel-packages] [Bug 2060268] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-545 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-550 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Noble: Fix Released Bug description: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init Beware that this has side-effects: see comment #37 [ Test Plan - Nvidia case ] 1. Set up a DESKTOP where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. [ Regression Test Plan - Intel/AMD graphics ] 1. Set up a machine with integrated graphics only. 2. Reboot. 3. Verify that you are able to log into the Ubuntu Desktop Wayland session. 4. Run `apt install nvidia-driver-535`. 5. Reboot. 6. Verify that you are able to log into the Ubuntu Desktop Wayland session. [ Regression Test Plan - Virtual machines ] 1. Set up a virtual machine without any graphics acceleration (vmware, virtio...) 2. Reboot. 3. Verify that you are able to log into the Ubuntu Desktop Wayland session. 4. Run `sudo apt install nvidia-driver-535`. 5. Reboot. 6. Verify that you are able to log into the Ubuntu Desktop Wayland session. 7. Optionally go back to point 4, and try with nvidia-driver-550. [ Regression Test Plan - Nvidia+LUKS ] 1. Set up a desktop machine (not a laptop) with an Nvidia GPU and encrypted disk. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot 4. Verify that you see the password prompt for decrypting the disk. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. One case where this could happen is if the Nvidia driver would allow being loaded even without any nvidia hardware present: if that is the case, "Regression Test Plan - Virtual machines" would fail. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No u
[Kernel-packages] [Bug 2077509] Re: Missing firmware for Intel(R) Wi-Fi 7 BE200 320MHz
** Tags added: verification-needed-noble -- 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/2077509 Title: Missing firmware for Intel(R) Wi-Fi 7 BE200 320MHz Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Noble: Fix Committed Status in linux-firmware source package in Oracular: Fix Released Bug description: [SRU Justification] [Impact] Missing iwlwifi for Intel BE200. ``` $ sudo dmesg|grep iwlwifi [ 3.274505] iwlwifi :82:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz [ 3.275097] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-92.ucode failed with error -2 [ 3.275115] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-91.ucode failed with error -2 [ 3.275128] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-90.ucode failed with error -2 [ 3.275129] iwlwifi :82:00.0: no suitable firmware found! [ 3.275131] iwlwifi :82:00.0: minimum version required: iwlwifi-gl-c0-fm-c0-90 [ 3.275132] iwlwifi :82:00.0: maximum version supported: iwlwifi-gl-c0-fm-c0-92 [ 3.275133] iwlwifi :82:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git ``` [Fix] Two upstream linux-firmware commits from upstream tag iwlwifi- fw-2024-07-23 fulfills the need. [Test Case] Expecting similar dmesg: ``` $ sudo dmesg|grep iwlwifi [ 2.548446] iwlwifi :82:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz [ 2.555076] iwlwifi :82:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.182.4.1 [ 2.07] iwlwifi :82:00.0: loaded firmware version 92.67ce4588.0 gl-c0-fm-c0-92.ucode op_mode iwlmvm [ 3.017113] iwlwifi :82:00.0: WRT: Invalid buffer destination [ 3.281636] iwlwifi :82:00.0: loaded PNVM version da3b5cf2 [ 3.302582] iwlwifi :82:00.0: Detected RF FM, rfid=0x112200 [ 3.402403] iwlwifi :82:00.0: base HW address: a0:02:a5:79:66:d4 [ 3.570939] iwlwifi :82:00.0 wlp130s0f0: renamed from wlan0 ``` [Where problems could occur] In kernels >= v6.11-rc1, the supported UCODE API range is [90, 92], and for v6.10 kernels [80, 90], v6.9 [80, 89], v6.8 [80, 86]. So this affects kernel >= 6.10, and for them BE200 is not supported yet. [Other Info] This affects kernel >= 6.10, and therefore Noble and Oracular should be in the list. While linux-firmware/oracular has included iwlwifi- fw-2024-07-23, it makes Noble the only one nominated for fixing. == original bug report == Got: $ sudo dmesg|grep iwlwifi [3.257466] iwlwifi :82:00.0: enabling device ( -> 0002) [3.274366] iwlwifi :82:00.0: Detected crf-id 0x2001910, cnv-id 0x2001910 wfpm id 0x8000 [3.274502] iwlwifi :82:00.0: PCI dev 272b/40f0, rev=0x472, rfid=0x112200 [3.274505] iwlwifi :82:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz [3.275097] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-92.ucode failed with error -2 [3.275115] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-91.ucode failed with error -2 [3.275128] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-90.ucode failed with error -2 [3.275129] iwlwifi :82:00.0: no suitable firmware found! [3.275131] iwlwifi :82:00.0: minimum version required: iwlwifi-gl-c0-fm-c0-90 [3.275132] iwlwifi :82:00.0: maximum version supported: iwlwifi-gl-c0-fm-c0-92 [3.275133] iwlwifi :82:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git Expecting: $ sudo dmesg|grep iwlwifi [2.541369] iwlwifi :82:00.0: enabling device ( -> 0002) [2.548367] iwlwifi :82:00.0: Detected crf-id 0x2001910, cnv-id 0x2001910 wfpm id 0x8000 [2.548444] iwlwifi :82:00.0: PCI dev 272b/40f0, rev=0x472, rfid=0x112200 [2.548446] iwlwifi :82:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz [2.555076] iwlwifi :82:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.182.4.1 [2.07] iwlwifi :82:00.0: loaded firmware version 92.67ce4588.0 gl-c0-fm-c0-92.ucode op_mode iwlmvm [3.017113] iwlwifi :82:00.0: WRT: Invalid buffer destination [3.281636] iwlwifi :82:00.0: loaded PNVM version da3b5cf2 [3.302582] iwlwifi :82:00.0: Detected RF FM, rfid=0x112200 [3.402403] iwlwifi :82:00.0: base HW address: a0:02:a5:79:66:d4 [3.570939] iwlwifi :82:00.0 wlp130s0f0: renamed from wlan0 [4.200554] iwlwifi :82:00.0: WRT: Invalid buffer destination [4.611030] iwlwifi :82:00.0: Registered PHC clock: iwlwifi-PTP, with index: 1 --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COM
[Kernel-packages] [Bug 2071698] Re: Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform
** 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/2071698
Title:
Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.11 source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Committed
Status in linux-firmware source package in Oracular:
Fix Released
Status in linux-oem-6.11 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
[Impact]
Starting from Intel Lunar Lake, the ISH firmware will reside in system
root as separated blobs, and the kernel driver is responsible for
loading a preferred one based on DMI info.
[Fix]
Kernel fixes in linux-next:
* aa4674c525e1e hid: intel-ish-hid: Add support for vendor customized
firmware loading
* 641361538b68d HID: intel-ish-hid: Use CPU generation string in driver_data
* 87de1615194ee Documentation: hid: intel-ish-hid: Add vendor custom firmware
loading
linux-firmware in upstream tag 20240709:
* 33a8b2a7f604 linux-firmware: Add ISH firmware file for Intel Lunar Lake
platform
[Test Case]
dmesg dumps:
```
intel_ish_ipc :00:12.0: ISH loader: firmware loaded. size:748032
ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done
OK, num_hid_devices=2
hid-generic 001F:8087:0AC2.0005: hidraw4: SENSOR HUB HID v2.00 Device
[hid-ishtp 8087:0AC2] on
hid-generic 001F:8087:0AC2.0006: hidraw5: SENSOR HUB HID v2.00 Device
[hid-ishtp 8087:0AC2] on
hid-sensor-hub 001F:8087:0AC2.0005: hidraw4: SENSOR HUB HID v2.00 Device
[hid-ishtp 8087:0AC2] on
hid-sensor-hub 001F:8087:0AC2.0006: hidraw5: SENSOR HUB HID v2.00 Device
[hid-ishtp 8087:0AC2] on
```
[Where problems could occur]
This is to include generic blob provided by Intel for all Lunar Lake
platforms. It may not be stable, may not be functional, and may have
various problems until the hardware vendor submit their own.
[Other Info]
Nominated for linux/oracular, linux-oem-6.11/noble, linux-
firmware/oracular and linux-firmware/noble.
== original bug report ==
* kernel
-
https://patchwork.kernel.org/project/linux-input/cover/20240813034736.812475-1-lixu.zh...@intel.com/
* linux-firmware
- generic
* commit 33a8b2a7f604 ("linux-firmware: Add ISH firmware file for Intel
Lunar Lake platform")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2071698/+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 2077487] Re: Broken atime in 2.2.2-0ubuntu9 (noble's version)
** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-hwe-6.8 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: zfs-linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-6.8 (Ubuntu) Status: New => Opinion ** Changed in: linux-hwe-6.8 (Ubuntu) Status: Opinion => Invalid ** Changed in: linux-hwe-6.8 (Ubuntu Noble) Status: New => Invalid ** Changed in: zfs-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.launchpad.net/bugs/2077487 Title: Broken atime in 2.2.2-0ubuntu9 (noble's version) Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in zfs-linux package in Ubuntu: Fix Released Status in linux source package in Noble: New Status in linux-hwe-6.8 source package in Noble: Invalid Status in zfs-linux source package in Noble: In Progress Bug description: 2.2.2-0ubuntu9 has the 6.7 compat series, including https://github.com/openzfs/zfs/commit/db4fc559cc1931b9219e62aa505cd5c51a17b232, but does not include the fix for that commit (affects both pre-6.7 and post-6.7), https://github.com/openzfs/zfs/commit/f0bf7a247dbb030d68c7fd2b5526dd111cc775d0. This manifests for me on the current (6.8.0-40.40~22.04.3) 22.04 HWE kernel as writes to a file resetting atime back to 0 (reads still seem to work as expected though given that state), which of course breaks real-world things (in my case, I can no longer successfully run LLVM's test suite). Thanks to CONFIG_INIT_STACK_ALL_ZERO=y being the default it seems like this isn't a kernel memory disclosure and is instead a deterministic use of 0, so I don't believe this to be a blatant security vulnerability. This also explains the behaviour observed above. This needs fixing in noble, and then propagating back through whatever kernels are pulling in this version, since linux-modules vendors copies of the pre-built DKMS modules, with the current 6.8 HWE kernel using 2.2.2-0ubuntu9 explicitly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077487/+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 2050083] Re: generate and ship vmlinux.h to allow packages to build BPF CO-RE
** Changed in: linux (Ubuntu) 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/2050083 Title: generate and ship vmlinux.h to allow packages to build BPF CO-RE Status in linux package in Ubuntu: Fix Committed Bug description: A vmlinux.h header generated from a kernel build with bpftool is needed to build and ship BPF CO-RE programs. We are looking to ship these in the next version of systemd. vmlinux.h being generated depends on the kernel version, architecture and kconfig. There are some vague promises of backward compatibility, but it is hard to gauge. We definitely do not want this file to be generated from the kernel running the build machine when building a package though, as very often these are very old and stable kernels building packages for the bleeding edge. In Fedora and now Debian we generate vmlinux.h at kernel package build time, and ship it with the other kernel headers (_not_ UAPI, the internal headers): https://salsa.debian.org/kernel- team/linux/-/commit/ac6f7eda4c3e8b0d0db20ad4bb8236371cf8d38e Please consider doing the same in Ubuntu's linux-headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2050083/+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 2076190] Re: perf build disables tracepoint support
** Changed in: linux (Ubuntu Oracular) Status: Confirmed => 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/2076190 Title: perf build disables tracepoint support Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Confirmed Status in linux source package in Oracular: Fix Committed Bug description: Since commit 92550b568d, the perf build for Ubuntu kernels does not link to libtraceevent, and thus cannot perform any operations on tracepoints, including processing perf.data files that contain tracepoint events. This is a significant loss of functionality. Attempts to utilize tracepoints fail with the following: perf record -e skb:kfree_skb event syntax error: 'skb:kfree_skb' \___ unsupported tracepoint libtraceevent is necessary for tracepoint support commit 92550b568d33f82de1ac24cb912082ff31aa43ba Author: Andrea Righi Date: Tue May 30 07:27:51 2023 +0200 UBUNTU: [Packaging] perf: build without libtraceevent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076190/+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 2076174] Re: noble/linux-oem-6.11: 6.11.0-1001.1 -proposed tracker
*** This bug is a duplicate of bug 2079016 *** https://bugs.launchpad.net/bugs/2079016 ** This bug is no longer a duplicate of bug 2078949 noble/linux-oem-6.11: 6.11.0-1003.3 -proposed tracker ** This bug has been marked a duplicate of bug 2079016 noble/linux-oem-6.11: 6.11.0-1004.4 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.11 in Ubuntu. https://bugs.launchpad.net/bugs/2076174 Title: noble/linux-oem-6.11: 6.11.0-1001.1 -proposed tracker Status in canonical-signing-jobs task00 series: Fix Released Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow abi-testing series: Invalid Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow new-review series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-generate series: Fix Released Status in Kernel SRU Workflow prepare-package-lrg series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-lrs series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow signing-signoff series: Fix Released Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux-oem-6.11 source package in Noble: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: from: aa77570705065ac8 route-entry: 1 delta: promote-to-proposed: [lrm, lrs, main, meta, signed, lrg, generate] flag: boot-testing-requested: true bugs-spammed: true proposed-testing-requested: true packages: generate: linux-generate-oem-6.11 lrg: linux-restricted-generate-oem-6.11 lrm: linux-restricted-modules-oem-6.11 lrs: linux-restricted-signatures-oem-6.11 main: linux-oem-6.11 meta: linux-meta-oem-6.11 signed: linux-signed-oem-6.11 phase: Testing phase-changed: Tuesday, 13. August 2024 08:35 UTC reason: regression-testing: Stalled -s testing FAILED synthetic: :promote-to-as-proposed: Fix Released variant: debs versions: lrm: 6.11.0-1001.1 main: 6.11.0-1001.1 meta: 6.11.0-1001.1 signed: 6.11.0-1001.1 ~~: clamps: new-review: aa77570705065ac8 promote-to-proposed: aa77570705065ac8 self: 6.11.0-1001.1 sru-review: aa77570705065ac8 tracker: last-message: '2024-08-13 07:48:49.587999+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2076174/+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 2076174] Re: noble/linux-oem-6.11: 6.11.0-1001.1 -proposed tracker
*** This bug is a duplicate of bug 2078949 *** https://bugs.launchpad.net/bugs/2078949 ** This bug is no longer a duplicate of bug 2077325 noble/linux-oem-6.11: 6.11.0-1002.2 -proposed tracker ** This bug has been marked a duplicate of bug 2078949 noble/linux-oem-6.11: 6.11.0-1003.3 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.11 in Ubuntu. https://bugs.launchpad.net/bugs/2076174 Title: noble/linux-oem-6.11: 6.11.0-1001.1 -proposed tracker Status in canonical-signing-jobs task00 series: Fix Released Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow abi-testing series: Invalid Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow new-review series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-generate series: Fix Released Status in Kernel SRU Workflow prepare-package-lrg series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-lrs series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow signing-signoff series: Fix Released Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux-oem-6.11 source package in Noble: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: from: aa77570705065ac8 route-entry: 1 delta: promote-to-proposed: [lrm, lrs, main, meta, signed, lrg, generate] flag: boot-testing-requested: true bugs-spammed: true proposed-testing-requested: true packages: generate: linux-generate-oem-6.11 lrg: linux-restricted-generate-oem-6.11 lrm: linux-restricted-modules-oem-6.11 lrs: linux-restricted-signatures-oem-6.11 main: linux-oem-6.11 meta: linux-meta-oem-6.11 signed: linux-signed-oem-6.11 phase: Testing phase-changed: Tuesday, 13. August 2024 08:35 UTC reason: regression-testing: Stalled -s testing FAILED synthetic: :promote-to-as-proposed: Fix Released variant: debs versions: lrm: 6.11.0-1001.1 main: 6.11.0-1001.1 meta: 6.11.0-1001.1 signed: 6.11.0-1001.1 ~~: clamps: new-review: aa77570705065ac8 promote-to-proposed: aa77570705065ac8 self: 6.11.0-1001.1 sru-review: aa77570705065ac8 tracker: last-message: '2024-08-13 07:48:49.587999+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2076174/+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 2078929] Re: Pull in latest X13s commits
** 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/2078929 Title: Pull in latest X13s commits Status in linux package in Ubuntu: Fix Committed Status in linux source package in Oracular: Fix Committed Bug description: There are a couple of X13s/sc8280xp related commits in linux-next and Johan's WIP tree that we should pull into 6.11 of Oracular. They fix a coupe of minor issues and enable Qualcomm's Venus video accelerator HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2078929/+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 2076209] Re: Intel Lunar Lake / Battlemage enablement
** Summary changed: - LNL/BMG enablement + Intel Lunar Lake / Battlemage enablement ** 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/2076209 Title: Intel Lunar Lake / Battlemage enablement Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.11 source package in Noble: New Status in linux source package in Oracular: Fix Committed Status in linux-oem-6.11 source package in Oracular: Invalid Bug description: [Impact] Intel Lunar Lake & Battlemage GPU's don't work in 24.10. [Fix] Backport commits from 6.12 to 6.11 in two batches, the second one dropping xe.force_probe requirement. [Test case] Boot the new kernel, check from dmesg that the drm driver is initialized correctly. [Where problems could occur] The backport is mostly confined in drm/xe, which isn't used by default on any hardware before LNL/BMG, so chance of regressions should be limited. Also, this backport is validated by the vendor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076209/+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 2076209] Re: LNL/BMG enablement
** Description changed: [Impact] Intel Lunar Lake & Battlemage GPU's don't work in 24.10. [Fix] - Backport commits from 6.12 to 6.11. + Backport commits from 6.12 to 6.11 in two batches, the second one + dropping xe.force_probe requirement. [Test case] Boot the new kernel, check from dmesg that the drm driver is initialized correctly. [Where problems could occur] The backport is mostly confined in drm/xe, which isn't used by default on any hardware before LNL/BMG, so chance of regressions should be limited. Also, this backport is validated by the vendor. -- 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/2076209 Title: LNL/BMG enablement Status in linux package in Ubuntu: In Progress Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.11 source package in Noble: New Status in linux source package in Oracular: In Progress Status in linux-oem-6.11 source package in Oracular: Invalid Bug description: [Impact] Intel Lunar Lake & Battlemage GPU's don't work in 24.10. [Fix] Backport commits from 6.12 to 6.11 in two batches, the second one dropping xe.force_probe requirement. [Test case] Boot the new kernel, check from dmesg that the drm driver is initialized correctly. [Where problems could occur] The backport is mostly confined in drm/xe, which isn't used by default on any hardware before LNL/BMG, so chance of regressions should be limited. Also, this backport is validated by the vendor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076209/+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 2076209] Re: LNL/BMG enablement
** Description changed: - Placeholder for backporting required fixes for Lunar Lake graphics. + [Impact] + + Intel Lunar Lake & Battlemage GPU's don't work in 24.10. + + [Fix] + + Backport commits from 6.12 to 6.11. + + [Test case] + + Boot the new kernel, check from dmesg that the drm driver is initialized + correctly. + + [Where problems could occur] + + The backport is mostly confined in drm/xe, which isn't used by default + on any hardware before LNL/BMG, so chance of regressions should be + limited. Also, this backport is validated by the vendor. ** Changed in: linux (Ubuntu Oracular) Status: New => In Progress ** Changed in: linux (Ubuntu Oracular) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/2076209 Title: LNL/BMG enablement Status in linux package in Ubuntu: In Progress Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.11 source package in Noble: New Status in linux source package in Oracular: In Progress Status in linux-oem-6.11 source package in Oracular: Invalid Bug description: [Impact] Intel Lunar Lake & Battlemage GPU's don't work in 24.10. [Fix] Backport commits from 6.12 to 6.11. [Test case] Boot the new kernel, check from dmesg that the drm driver is initialized correctly. [Where problems could occur] The backport is mostly confined in drm/xe, which isn't used by default on any hardware before LNL/BMG, so chance of regressions should be limited. Also, this backport is validated by the vendor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076209/+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 2077922] Re: Missing device ID for amd_atl for AMD platforms Kraken and Strix-Halo
** Summary changed: - Missing device ID for amd_atl for AMD platforms Kracken and Strix-Halo + Missing device ID for amd_atl for AMD platforms Kraken and Strix-Halo -- 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/2077922 Title: Missing device ID for amd_atl for AMD platforms Kraken and Strix-Halo Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-oem-6.11 source package in Noble: In Progress Status in linux source package in Oracular: In Progress Status in linux-oem-6.11 source package in Oracular: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2077922 [Impact] amd_atl driver doesn't work on AMD platforms Kracken and Strix-Halo. $ dmesg | grep amd_atl amd_atl: Failed to determine DF Revision [Fix] Two upstream commits that are already in linux-next: * 59c34008d3bd x86/amd_nb: Add new PCI IDs for AMD family 1Ah model 60h * 0f70fdd42559 x86/amd_nb: Add new PCI IDs for AMD family 1Ah model 60h-70h [Test Case] When correctly enabled, there should be following messages in dmesg output: $ dmesg | grep amd_atl amd_atl: AMD Address Translation Library initialized [Where problems could occur] New hardware support. [Other Info] This targets kernel v6.10+, which makes linux/oracular and linux- oem-6.11/noble, linux-unstable/oracular the only three targets. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:ubuntu 2370 F pipewire /dev/snd/controlC2: ubuntu 2373 F wireplumber /dev/snd/controlC0: ubuntu 2373 F wireplumber /dev/snd/controlC1: ubuntu 2373 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-05-07 (119 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) IwConfig: lono wireless extensions. enp193s0f0 no wireless extensions. MachineType: AMD MAPLE Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-1002-oem root=UUID=ff988e57-9bf4-46d6-94cf-1e35d0139e12 ro amdgpu.ip_block_mask=0xfcff quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.11.0-1002.2-oem 6.11.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.11.0-1002-oem N/A linux-backports-modules-6.11.0-1002-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.3+exp.17 RfKill: Tags: noble Uname: Linux 6.11.0-1002-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/25/2024 21:25:16 dmi.bios.release: 0.0 dmi.bios.vendor: AMD dmi.bios.version: RG60061C dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: MAPLE-STXH dmi.board.vendor: AMD dmi.board.version: RevB dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: 12345 dmi.ec.firmware.release: 0.23 dmi.modalias: dmi:bvnAMD:bvrRG60061C:bd04/25/2024212516:br0.0:efr0.23:svnAMD:pnMAPLE:pvrRG60061C:rvnAMD:rnMAPLE-STXH:rvrRevB:cvnAMD:ct10:cvr12345:sku12345678: dmi.product.family: STXH dmi.product.name: MAPLE dmi.product.sku: 12345678 dmi.product.version: RG60061C dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2077922/+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 1920180] Re: Can't detect intel wifi 6235
after over three years the patch still hasn't made it upstream -- 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/1920180 Title: Can't detect intel wifi 6235 Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] Wifi doesn't work on systems with Centrino Advanced-N 6235 [8086:526a]. [Fix] The patch adds the device ID 0x526A. [Test Case] Wifi works after installing test kernel (#19 & #20 in LP:1920180) [Regression Potential] Low to none. This adds a hardware ID and does not affects systems output such a wifi card. [Note] Patch was also sent for upstream reviews and can be viewed at https://www.spinics.net/lists/stable/msg452937.html == Original descriptions Can't detect Wireless intel advance 6235 03:00.0 Network controller [0280]: Intel Corporation Centrino Advanced-N 6235 [8086:088f] (rev 24) Subsystem: Intel Corporation Centrino Advanced-N 6235 [8086:526a] Flags: fast devsel, IRQ 255 Memory at e040 (64-bit, non-prefetchable) [size=8K] Capabilities: --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sgo1245 F pulseaudio /dev/snd/controlC0: sgo1245 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.1 InstallationDate: Installed on 2021-03-15 (4 days ago) InstallationMedia: Linux Mint 20.1 "Ulyssa" - Release amd64 20210103 IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: LENOVO 20AWS0DS0T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=7bbc36d4-b65d-4291-a3b9-dc840a88f20a ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no Tags: ulyssa Uname: Linux 5.4.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: GLETA1WW (2.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AWS0DS0T dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLETA1WW(2.55):bd04/20/2020:svnLENOVO:pn20AWS0DS0T:pvrThinkPadT440p:rvnLENOVO:rn20AWS0DS0T:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AWS0DS0T dmi.product.sku: LENOVO_MT_20AW_BU_Think_FM_ThinkPad T440p dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920180/+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 2073583] Re: [SRU][22.04.5]: mpi3mr driver update
this is included in 6.11-rc which is in oracular-proposed ** 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/2073583 Title: [SRU][22.04.5]: mpi3mr driver update Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Won't Fix Status in linux source package in Noble: Fix Committed Status in linux source package in Oracular: Fix Committed Bug description: [Impact] This update has been initiated to incorporate the mpi3mr driver from upstream into the upcoming Ubuntu releases (Ubuntu 22.04.x point releases). [Fix] - cf82b9e866b6 : mpi3mr: Driver version update - 1c342b0548e3 : mpi3mr: Prevent PCI writes from driver during PCI error recovery - 30bafe1774f0 : mpi3mr: Support PCI Error Recovery callback handlers - 78b506984ebe : mpi3mr: Add ioctl support for HDB - d8d08d1638ce : mpi3mr: Trigger support - fc941140: mpi3mr: HDB allocation and posting for hardware and firmware buffers [Test Plan] - Driver load/unload - ro and r1 creation and deletion - By using management command tested hdb - Use sg_reset -H - Resetting the controller in a loop. [Where problems could occur] [Other Info] noble https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2073583_mpi3mr_update oracular https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/oracular/+ref/lp_2073583_mpi3mr_update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073583/+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 1921137] Re: mount.ocfs2 causes kernel BUG at lib/string.c:1149!
commit b15fa9224e6e1239414525d8d556d824701849fc Author: Valentin Vidic Date: Mon Oct 18 15:15:42 2021 -0700 ocfs2: mount fails with buffer overflow in strlen ** Changed in: linux (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921137 Title: mount.ocfs2 causes kernel BUG at lib/string.c:1149! Status in corosync package in Ubuntu: Confirmed Status in libaio package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in ocfs2-tools package in Ubuntu: Confirmed Bug description: the ocfs2-tools autopkgtests for hirsute recently started failing, and a local test run shows this kernel bug occurring during the test: [ 100.791586] o2dlm: Leaving domain 1D5A19C6EC8F430AB4E29230BC54D70E [ 108.864491] detected buffer overflow in strlen [ 108.869193] [ cut here ] [ 108.869196] kernel BUG at lib/string.c:1149! [ 108.869962] invalid opcode: [#1] SMP PTI [ 108.870715] CPU: 15 PID: 1725 Comm: mount.ocfs2 Not tainted 5.11.0-11-generic #12-Ubuntu [ 108.872156] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 [ 108.873701] RIP: 0010:fortify_panic+0x13/0x15 [ 108.874452] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8 [ 108.879043] RSP: 0018:a9cf811afc90 EFLAGS: 00010246 [ 108.880396] RAX: 0022 RBX: 926a4cd06000 RCX: [ 108.882165] RDX: RSI: 926b77bd8ac0 RDI: 926b77bd8ac0 [ 108.883474] RBP: a9cf811afc90 R08: R09: a9cf811afa88 [ 108.884758] R10: a9cf811afa80 R11: 92f53508 R12: 0004 [ 108.885961] R13: 926a49917800 R14: 926a54bdc800 R15: 926a4cd06291 [ 108.887163] FS: 7f8440b60600() GS:926b77bc() knlGS: [ 108.888626] CS: 0010 DS: ES: CR0: 80050033 [ 108.889607] CR2: 55eec2b97dc8 CR3: 000106c64000 CR4: 06e0 [ 108.890823] Call Trace: [ 108.891279] ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2] [ 108.892603] ? ocfs2_sb_probe+0x133/0x3a0 [ocfs2] [ 108.893484] ? pointer+0x185/0x4d0 [ 108.894079] ocfs2_fill_super+0x15d/0x7a0 [ocfs2] [ 108.894965] mount_bdev+0x18d/0x1c0 [ 108.895570] ? ocfs2_remount+0x450/0x450 [ocfs2] [ 108.896518] ocfs2_mount+0x15/0x20 [ocfs2] [ 108.897293] legacy_get_tree+0x2b/0x50 [ 108.897939] vfs_get_tree+0x2a/0xc0 [ 108.898542] do_new_mount+0x14b/0x1a0 [ 108.899175] path_mount+0x1d4/0x4e0 [ 108.899789] __x64_sys_mount+0x108/0x140 [ 108.900465] do_syscall_64+0x38/0x90 [ 108.901129] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 108.902376] RIP: 0033:0x7f8441109bce [ 108.903169] Code: 48 8b 0d 9d 72 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6a 72 0c 00 f7 d8 64 89 01 48 [ 108.906322] RSP: 002b:7fff92a4e2f8 EFLAGS: 0246 ORIG_RAX: 00a5 [ 108.907610] RAX: ffda RBX: RCX: 7f8441109bce [ 108.909000] RDX: 55eec0e140ae RSI: 55eec2b899e0 RDI: 55eec2b8f060 [ 108.910727] RBP: 7fff92a4e4a0 R08: 55eec2b8f000 R09: 7fff92a4bd00 [ 108.912443] R10: R11: 0246 R12: 7fff92a4e390 [ 108.914190] R13: 7fff92a4e310 R14: 55eec2b8ac00 R15: [ 108.916009] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue 9p fscache nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev bochs_drm drm_vram_helper drm_ttm_helper ttm kvm_intel drm_kms_helper parport_pc 9pnet_virtio cec input_leds joydev 9pnet parport rc_core fb_sys_fops serio_raw kvm syscopyarea sysfillrect sysimgblt mac_hid qemu_fw_cfg sch_fq_codel msr drm virtio_rng ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover virtio_blk i2c_piix4 pata_acpi floppy [ 108.925313] ---[ end trace 72e4f69b08b1a89a ]--- [ 108.927136] RIP: 0010:fortify_panic+0x13/0x15 [ 108.928706] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8 [ 108.932308] RSP: 0018:a9cf811afc90 EFLAGS: 00010246 [ 108.933231] RAX: 0022 RBX: 926a4cd06000 RCX: [ 108.934468] RDX: RSI: 926b77bd8ac0 RDI: 926b77bd8ac0 [ 108.935659] RBP: a9cf811afc90 R08: 000
[Kernel-packages] [Bug 1921137] Re: mount.ocfs2 causes kernel BUG at lib/string.c:1149!
seems to have been fixed at some point for the kernel ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921137 Title: mount.ocfs2 causes kernel BUG at lib/string.c:1149! Status in corosync package in Ubuntu: Confirmed Status in libaio package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in ocfs2-tools package in Ubuntu: Confirmed Bug description: the ocfs2-tools autopkgtests for hirsute recently started failing, and a local test run shows this kernel bug occurring during the test: [ 100.791586] o2dlm: Leaving domain 1D5A19C6EC8F430AB4E29230BC54D70E [ 108.864491] detected buffer overflow in strlen [ 108.869193] [ cut here ] [ 108.869196] kernel BUG at lib/string.c:1149! [ 108.869962] invalid opcode: [#1] SMP PTI [ 108.870715] CPU: 15 PID: 1725 Comm: mount.ocfs2 Not tainted 5.11.0-11-generic #12-Ubuntu [ 108.872156] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 [ 108.873701] RIP: 0010:fortify_panic+0x13/0x15 [ 108.874452] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8 [ 108.879043] RSP: 0018:a9cf811afc90 EFLAGS: 00010246 [ 108.880396] RAX: 0022 RBX: 926a4cd06000 RCX: [ 108.882165] RDX: RSI: 926b77bd8ac0 RDI: 926b77bd8ac0 [ 108.883474] RBP: a9cf811afc90 R08: R09: a9cf811afa88 [ 108.884758] R10: a9cf811afa80 R11: 92f53508 R12: 0004 [ 108.885961] R13: 926a49917800 R14: 926a54bdc800 R15: 926a4cd06291 [ 108.887163] FS: 7f8440b60600() GS:926b77bc() knlGS: [ 108.888626] CS: 0010 DS: ES: CR0: 80050033 [ 108.889607] CR2: 55eec2b97dc8 CR3: 000106c64000 CR4: 06e0 [ 108.890823] Call Trace: [ 108.891279] ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2] [ 108.892603] ? ocfs2_sb_probe+0x133/0x3a0 [ocfs2] [ 108.893484] ? pointer+0x185/0x4d0 [ 108.894079] ocfs2_fill_super+0x15d/0x7a0 [ocfs2] [ 108.894965] mount_bdev+0x18d/0x1c0 [ 108.895570] ? ocfs2_remount+0x450/0x450 [ocfs2] [ 108.896518] ocfs2_mount+0x15/0x20 [ocfs2] [ 108.897293] legacy_get_tree+0x2b/0x50 [ 108.897939] vfs_get_tree+0x2a/0xc0 [ 108.898542] do_new_mount+0x14b/0x1a0 [ 108.899175] path_mount+0x1d4/0x4e0 [ 108.899789] __x64_sys_mount+0x108/0x140 [ 108.900465] do_syscall_64+0x38/0x90 [ 108.901129] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 108.902376] RIP: 0033:0x7f8441109bce [ 108.903169] Code: 48 8b 0d 9d 72 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6a 72 0c 00 f7 d8 64 89 01 48 [ 108.906322] RSP: 002b:7fff92a4e2f8 EFLAGS: 0246 ORIG_RAX: 00a5 [ 108.907610] RAX: ffda RBX: RCX: 7f8441109bce [ 108.909000] RDX: 55eec0e140ae RSI: 55eec2b899e0 RDI: 55eec2b8f060 [ 108.910727] RBP: 7fff92a4e4a0 R08: 55eec2b8f000 R09: 7fff92a4bd00 [ 108.912443] R10: R11: 0246 R12: 7fff92a4e390 [ 108.914190] R13: 7fff92a4e310 R14: 55eec2b8ac00 R15: [ 108.916009] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue 9p fscache nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev bochs_drm drm_vram_helper drm_ttm_helper ttm kvm_intel drm_kms_helper parport_pc 9pnet_virtio cec input_leds joydev 9pnet parport rc_core fb_sys_fops serio_raw kvm syscopyarea sysfillrect sysimgblt mac_hid qemu_fw_cfg sch_fq_codel msr drm virtio_rng ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover virtio_blk i2c_piix4 pata_acpi floppy [ 108.925313] ---[ end trace 72e4f69b08b1a89a ]--- [ 108.927136] RIP: 0010:fortify_panic+0x13/0x15 [ 108.928706] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8 [ 108.932308] RSP: 0018:a9cf811afc90 EFLAGS: 00010246 [ 108.933231] RAX: 0022 RBX: 926a4cd06000 RCX: [ 108.934468] RDX: RSI: 926b77bd8ac0 RDI: 926b77bd8ac0 [ 108.935659] RBP: a9cf811afc90 R08: R09: a9cf811afa88 [ 108.936933] R10: a9cf811afa80 R11: 92f53508 R12:
[Kernel-packages] [Bug 1960841] Re: Make linux-tools-common Provide linux-cpupower
** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1960841 Title: Make linux-tools-common Provide linux-cpupower Status in linux package in Ubuntu: In Progress Status in opa-ff package in Ubuntu: Confirmed Bug description: In Debian, the tools cpupower, turbostat and x86_energy_perf_policy are packaged in linux-cpupower. In turn, some packages that use those CLI tools depend on this package. Currently on Debian sid, we have ❯ reverse-depends linux-cpupower Reverse-Recommends * tuned Reverse-Depends * opa-basic-tools [amd64 Having linux-tools-common Providing linux-cpupower would allow us to keep the aforementioned packages in sync with Debian without introducing a delta. While this is related to https://bugs.launchpad.net/ubuntu/+source/opa-ff/+bug/1215411 it is *not* the same issue, as we're not dealing with the libraries but with the CLI tools. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960841/+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 2060101] Re: Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera
** Description changed:
[SRU Justification]
[Impact]
Outdated ACPI ID used in previous revisions, and the production one is
finally supported in a recent upstream WW3224-USBIO-PV-HFIX1 release.
[Fix]
https://github.com/intel/usbio-
drivers/commit/fc527affa4654468cdb63f8803eacd1a71b02017
[Test Case]
- Install the built dkms binary package and linux-headers-generic-
- hwe-22.04/jammy. The dkms build should be triggered and complete
- successfully, and the devices with BIOS of 69W or a newer version should
- work as usual.
+ Install the built dkms binary package on a noble system with GA kernel
+ headers. The dkms build should be triggered and complete successfully,
+ and the devices with BIOS of 69W or a newer version should work as
+ usual.
[Where problems could occur]
It appears the i2c protocol meant to be governed by this usbio is not in
well control by the upstream collaborative peers, such that we fell into
various problems due the the mismatch of firmware version, and therefore
some ugly patch from Intel was added to work-around that. While we don't
have too much details about the design and the solution, all we can do
is to deploy extensive tests as possible.
[Other Info]
While linux-hwe-6.8 uses usbio-drivers/noble, the nominated candidates
are Oracular and Noble.
== kernel SRU ==
[Impact]
ov08x40 camera sensor is not working on IPU6 platforms.
[Fix]
A few changes from upstream kernel as well as a not yet upstreamed patch in
the Intel ipu6-drivers GitHub repo.
* commit b1a42fde ("media: ov08x40: Avoid sensor probing in D0 state")
* commit eea8f730 ("media: ov08x40: Modify the tline calculation in different
modes")
*
https://github.com/intel/ipu6-drivers/blob/Release_20240624/patch/v6.8/0001-media-ov08x40-Add-Tline-calculation-and-handshake-pi.patch
[Test Case]
The proposed kernel should have been built along with the updated
ipu6-drivers dkms. To verify ipu6-drivers alone, one will need
experimental kernels from https://launchpad.net/~canonical-hwe-
team/+archive/ubuntu/intermediate-kernel.
Here are steps for verifying kernels from -proposed pocket:
1. test camera after rebooting into a proposed kernel,
2. run suspend/resume stress test plan.
3. verify camera still working
[Where problems could occur]
These fixes are quite limited to ipu6/ivsc platforms, and affected no
power-consumption or other noticible problem.
[Other Info]
The fixing commits/patches were meant for in-tree driver, but yet it
changes device power up sequence and may affect platforms not interested
in IPU6 enablement. It is then duplicated into ipu6-drivers dkms to
avoid any unexpected side effect.
While some of the fixes are still under upstream review, meaning they're
not yet available in any kernel release, linux-unstable/oracular/noble
and oem-6.8/6.1x will be nominated for a rebuild against new dkms.
--
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/2060101
Title:
Enable OV08X40 camera sensor for Intel MTL IPU6 MIPI Camera
Status in HWE Next:
New
Status in ipu6-drivers package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-6.10 package in Ubuntu:
Invalid
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in usbio-drivers package in Ubuntu:
Fix Released
Status in ipu6-drivers source package in Jammy:
Won't Fix
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.10 source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in linux-oem-6.8 source package in Jammy:
Invalid
Status in usbio-drivers source package in Jammy:
Invalid
Status in ipu6-drivers source package in Noble:
Fix Released
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.10 source package in Noble:
Fix Released
Status in linux-oem-6.5 source package in Noble:
Invalid
Status in linux-oem-6.8 source package in Noble:
Fix Released
Status in usbio-drivers source package in Noble:
Fix Committed
Status in ipu6-drivers source package in Oracular:
Fix Released
Status in linux source package in Oracular:
Triaged
Status in linux-oem-6.10 source package in Oracular:
Invalid
Status in linux-oem-6.5 source package in Oracular:
Invalid
Status in linux-oem-6.8 source package in Oracular:
Invalid
Status in usbio-drivers source package in Oracular:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Outdated ACPI ID used in previous revisions, and the production one is
finally supported in a recent upstream WW3224-USBIO-PV-HFIX1 release.
[Fix]
https://github.com/intel/usbio-
drivers/commit/fc527affa4654468cdb63f8803eacd1a71b02017
[Kernel-packages] [Bug 2071774] Re: zfs-dkms FTBFS on Linux 6.10/s390x
builds fine now https://autopkgtest.ubuntu.com/packages/z/zfs-linux/oracular/s390x ** Changed in: zfs-linux (Ubuntu Oracular) Status: In Progress => Fix Released -- 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/2071774 Title: zfs-dkms FTBFS on Linux 6.10/s390x Status in Ubuntu on IBM z Systems: In Progress Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Oracular: Fix Released Bug description: ZFS FTBFS on Linux 6.10/s390x - full build log: https://launchpadlibrarian.net/737125941/buildlog_ubuntu- oracular-s390x.linux-unstable_6.10.0-12.12_BUILDING.txt.gz ``` CC [M] <>/build/zfs/2.2.4/build/module/os/linux/zfs/zvol_os.o LD [M] <>/build/zfs/2.2.4/build/module/spl.o LD [M] <>/build/zfs/2.2.4/build/module/zfs.o MODPOST <>/build/zfs/2.2.4/build/module/Module.symvers ERROR: modpost: GPL-incompatible module zfs.ko uses GPL-only symbol 'vm_layout' make[6]: *** [scripts/Makefile.modpost:145: <>/build/zfs/2.2.4/build/module/Module.symvers] Error 1 make[5]: *** [<>/headers/linux-headers-6.10.0-12-generic/Makefile:1891: modpost] Error 2 ``` same issue is 100% reproducible with upstream zfs (plus the 6.10 compatiblity patches on top): https://github.com/openzfs/zfs/pull/16250#issuecomment-2202351855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2071774/+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 2060268] Re: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver
answer to the first question forwarded from mattermost: "the simpledrm master device is never useful with another real DRM device, so yes it is safe" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2060268 Title: Phantom "Unknown Display" shown in Settings after installing the Nvidia driver Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers-470 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-545 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-550 package in Ubuntu: Won't Fix Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Noble: In Progress Bug description: [ Impact ] After installing Nvidia driver 545 on a single (27") monitor system, Settings shows a phantom 46" monitor of the same resolution. It looks like the phantom monitor is /dev/dri/card0 which is still controlled by simpledrm, while Nvidia uses /dev/dri/card1. This also seems to be triggering bug 2062426 and bug 2066126. [ Temporary Workaround ] 1. sudo rm /dev/dri/card0 2. Log in again. [ Permanent Workaround ] Add kernel parameter: initcall_blacklist=simpledrm_platform_driver_init [ Test Plan ] 1. Set up a single monitor desktop where the only GPU enabled is an Nvidia one. 2. Open the 'Additional Drivers' app to install a supported Nvidia driver. 3. Reboot and verify the Nvidia driver is now active (lspci -k should mention 'nvidia' and not 'nouveau'). 4. Open Settings and verify the only monitors shown are your real monitors. [ Where problems could occur ] Removing the simpledrm card is only safe when it's not being used. If somehow a machine wasn't using the installed Nvidia driver then there could be a risk of deleting the only working display. [ Other Info ] ProblemType: Bug ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:dan4631 F pipewire /dev/snd/controlC1: dan4636 F wireplumber CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-01-04 (92 days ago) InstallationMedia: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127) MachineType: Intel(R) Client Systems NUC12DCMi7 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 simpledrmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=8434774e-88f2-4e3f-adb8-2eb07dff3cf9 ro quiet loglevel=3 splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.8.0-11-generic N/A linux-backports-modules-6.8.0-11-generic N/A linux-firmware20240318.git3b128b60-0ubuntu1 Tags: noble Uname: Linux 6.8.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 12/20/2021 dmi.bios.release: 5.24 dmi.bios.vendor: Intel Corp. dmi.bios.version: EDADL579.0046.2021.1220.2351 dmi.board.name: NUC12EDBi7 dmi.board.vendor: Intel Corporation dmi.board.version: M27908-302 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 3.7 dmi.modalias: dmi:bvnIntelCorp.:bvrEDADL579.0046.2021.1220.2351:bd12/20/2021:br5.24:efr3.7:svnIntel(R)ClientSystems:pnNUC12DCMi7:pvrM30143-302:rvnIntelCorporation:rnNUC12EDBi7:rvrM27908-302:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12DCMi7: dmi.product.family: DC dmi.product.name: NUC12DCMi7 dmi.product.sku: RNUC12DCMi7 dmi.product.version: M30143-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2060268/+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 2076180] Re: Add new firmwares for 6.8 hwe kernel
** Changed in: linux-firmware (Ubuntu) Status: Triaged => Invalid -- 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/2076180 Title: Add new firmwares for 6.8 hwe kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] The 6.8 HWE kernel requires firmware that is not (yet) provided by linux-firmware in Jammy. This obviously results in non-functional HW components. [Fix] Add missing firmware blobs and links. [Test Case] Ideally: Verify that the 6.8 kernel loads the new firmware blobs and the affected HW components function as expected. Realistically: Mostly untestable due to lack of availability of relevant HW. [Where Problems Could Occur] This adds only new firmware blobs (and symbolic links) that the 5.15 GA kernel doesn't care about so should not introduce any issues. In case that's an incorrect assumption, some HW components might not function properly if the new blobs are incompatible with the 5.15 GA kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2076180/+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 2077112] Re: Missing Huc/Gsc support for Intel GFX Xe driver for Lunar Lake
Hello You-Sheng, or anyone else affected,
Accepted linux-firmware into noble-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/20240318.git3b128b60-0ubuntu2.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-
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.
** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2077112
Title:
Missing Huc/Gsc support for Intel GFX Xe driver for Lunar Lake
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-firmware source package in Oracular:
Fix Released
Bug description:
[Impact]
Missing Huc/Gsc firmware for Intel GFX Xe driver for Lunar Lake.
[Fix]
Few commits from upstream tag intel-2024-08-02.
[Test Case]
In dmesg:
```
xe :00:02.0: [drm] Found LUNARLAKE (device ID 64a0) display version 20.00
xe :00:02.0: [drm] Using GuC firmware from xe/lnl_guc_70.bin version
70.29.2
xe :00:02.0: [drm] Using GuC firmware from xe/lnl_guc_70.bin version
70.29.2
xe :00:02.0: [drm] Using HuC firmware from xe/lnl_huc.bin version 9.4.13
xe :00:02.0: [drm] Using GSC firmware from xe/lnl_gsc_1.bin version
104.0.0.1161
```
[Where problems could occur]
There has been one Xe fw at intel/lnl_guc_70.bin, and the other Xe
binaries are to complete Xe driver support on Lunar Lake. No known
issue so far.
[Other Info]
For Oracular, it has been included in version
20240808.gite131a437-0ubuntu1, leaving Noble as the only target of the
nomination for OEM-6.11.
== original bug report ==
* Kernel
-
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=e814902866ed22bc07d2af1303f3183357a438e8
("drm/xe/huc: Define HuC binary for LNL")
-
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=f4aa02c43969c36213a7fd4e56831693fc83ec4b
("drm/xe/gsc: Define GSC binary for LNL")
-
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=4eb0aab6e4434ada240286d934651dfdb2e08301
("drm/xe/guc: Bump minimum required GuC version to v70.29.2")
* linux-firmware
-
https://lore.kernel.org/linux-firmware/20240802175932.784781-1-daniele.ceraolospu...@intel.com/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2077112/+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 2077296] Re: Add more region support of QCOM WiFi WCN7850
Hello AaronMa, or anyone else affected, Accepted linux-firmware into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20240318.git3b128b60-0ubuntu2.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- 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. ** Changed in: linux-firmware (Ubuntu Oracular) Status: New => Fix Committed ** Changed in: linux-firmware (Ubuntu Noble) Status: New => Fix Committed -- 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/2077296 Title: Add more region support of QCOM WiFi WCN7850 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Committed Status in linux-firmware source package in Oracular: Fix Committed Bug description: [Impact] Qualcomm WiFi chip WCN7850 needs new board-2.bin for more regions. [Fix] Update board-2.bin in linux-firmware. [Test] Boot up, and WiFi works fine. [Where problems could occur] It may break Qualcomm WiFi WCN7850. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2077296/+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 2077509] Re: Missing firmware for Intel(R) Wi-Fi 7 BE200 320MHz
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20240318.git3b128b60-0ubuntu2.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- 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. ** Changed in: linux-firmware (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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2077509 Title: Missing firmware for Intel(R) Wi-Fi 7 BE200 320MHz Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Noble: Fix Committed Status in linux-firmware source package in Oracular: Fix Released Bug description: [SRU Justification] [Impact] Missing iwlwifi for Intel BE200. ``` $ sudo dmesg|grep iwlwifi [ 3.274505] iwlwifi :82:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz [ 3.275097] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-92.ucode failed with error -2 [ 3.275115] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-91.ucode failed with error -2 [ 3.275128] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-90.ucode failed with error -2 [ 3.275129] iwlwifi :82:00.0: no suitable firmware found! [ 3.275131] iwlwifi :82:00.0: minimum version required: iwlwifi-gl-c0-fm-c0-90 [ 3.275132] iwlwifi :82:00.0: maximum version supported: iwlwifi-gl-c0-fm-c0-92 [ 3.275133] iwlwifi :82:00.0: check git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git ``` [Fix] Two upstream linux-firmware commits from upstream tag iwlwifi- fw-2024-07-23 fulfills the need. [Test Case] Expecting similar dmesg: ``` $ sudo dmesg|grep iwlwifi [ 2.548446] iwlwifi :82:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz [ 2.555076] iwlwifi :82:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.182.4.1 [ 2.07] iwlwifi :82:00.0: loaded firmware version 92.67ce4588.0 gl-c0-fm-c0-92.ucode op_mode iwlmvm [ 3.017113] iwlwifi :82:00.0: WRT: Invalid buffer destination [ 3.281636] iwlwifi :82:00.0: loaded PNVM version da3b5cf2 [ 3.302582] iwlwifi :82:00.0: Detected RF FM, rfid=0x112200 [ 3.402403] iwlwifi :82:00.0: base HW address: a0:02:a5:79:66:d4 [ 3.570939] iwlwifi :82:00.0 wlp130s0f0: renamed from wlan0 ``` [Where problems could occur] In kernels >= v6.11-rc1, the supported UCODE API range is [90, 92], and for v6.10 kernels [80, 90], v6.9 [80, 89], v6.8 [80, 86]. So this affects kernel >= 6.10, and for them BE200 is not supported yet. [Other Info] This affects kernel >= 6.10, and therefore Noble and Oracular should be in the list. While linux-firmware/oracular has included iwlwifi- fw-2024-07-23, it makes Noble the only one nominated for fixing. == original bug report == Got: $ sudo dmesg|grep iwlwifi [3.257466] iwlwifi :82:00.0: enabling device ( -> 0002) [3.274366] iwlwifi :82:00.0: Detected crf-id 0x2001910, cnv-id 0x2001910 wfpm id 0x8000 [3.274502] iwlwifi :82:00.0: PCI dev 272b/40f0, rev=0x472, rfid=0x112200 [3.274505] iwlwifi :82:00.0: Detected Intel(R) Wi-Fi 7 BE200 320MHz [3.275097] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-92.ucode failed with error -2 [3.275115] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-91.ucode failed with error -2 [3.275128] iwlwifi :82:00.0: Direct firmware load for iwlwifi-gl-c0-fm-c0-90.ucode failed with error -2 [3.275129] iwlwifi :82:00.0: no suitable firmware found! [3.275131] iwlwifi :82:00.0: minimum version required: iwlwifi-gl-c0-fm-c0-90 [3.275132] iwlwifi :82:00.0: maximum version supported: iwlwifi-gl-c0-fm-c0-9
[Kernel-packages] [Bug 2071821] Re: Support Intel IPU7 MIPI camera
Hello You-Sheng, or anyone else affected, Accepted linux-firmware into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20240318.git3b128b60-0ubuntu2.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- 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. ** Changed in: linux-firmware (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/2071821 Title: Support Intel IPU7 MIPI camera Status in linux package in Ubuntu: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux source package in Noble: Invalid Status in linux-firmware source package in Noble: Fix Committed Status in linux-oem-6.11 source package in Noble: New Status in linux source package in Oracular: New Status in linux-firmware source package in Oracular: In Progress Status in linux-oem-6.11 source package in Oracular: Invalid Bug description: [SRU Justification] [Impact] Missing ipu7 firmware for Intel IPU7 MIPI camera platforms. [Fix] https://github.com/intel/ipu7-camera- bins/commit/398589deb5f8e7d16d13f0e12f0b49977f464594 [Test Case] With a working driver and the firmware in position, there should be messages in dmesg output: ``` kernel: intel-ipu7 intel-ipu7: cpd file name: intel/ipu/ipu7_fw.bin kernel: intel-ipu7 intel-ipu7: FW binary0 info: kernel: intel-ipu7 intel-ipu7: Name: psys kernel: intel-ipu7 intel-ipu7: Version: 1.1.9.240627135220 kernel: intel-ipu7 intel-ipu7: Timestamp: build_id:331942702 kernel: intel-ipu7 intel-ipu7: Commit: commit_id:d84f5c35 kernel: intel-ipu7 intel-ipu7: FW binary1 info: kernel: intel-ipu7 intel-ipu7: Name: isys kernel: intel-ipu7 intel-ipu7: Version: 1.1.9.240627135318 kernel: intel-ipu7 intel-ipu7: Timestamp: build_id:3823931988 kernel: intel-ipu7 intel-ipu7: Commit: commit_id:d84f5c35 ``` [Where problems could occur] New hardware. No know issue yet. [Other Info] This is the firmware part only, and the whole framework has to be enabled with both firmware, kernel driver and userspace HAL. Nominate for Noble and Oracular. == original bug report = Kernel drivers: * https://github.com/intel/ipu7-drivers * https://github.com/intel/vision-drivers * https://github.com/intel/usbio-drivers Kernel tree patch: * https://github.com/intel/ivsc-driver/commit/47e7c4a446c8ea8c741ff5a32fa7b19f9e6fd47e linux-firmware: * https://github.com/intel/ipu7-camera-bins Userspace frameworks: * To be discussed. --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:ubuntu 1247 F pipewire CRDA: N/A CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs ./boot/grub/grub.cfg CasperMD5CheckResult: fail Dependencies: firmware-sof-signed 2023.12.1-1ubuntu1+exp.5 [origin: unknown] DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04b-edge-20240821-70 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-08-22 (4 days ago) InstallationMedia: Ubuntu OEM 24.04 LTS "Noble Numbat" - Release amd64 (20240820) IwConfig: lono wireless extensions. enx00e04c6801fa no wireless extensions. MachineType: Dell Inc. XPS 13 9350 Package: linux-firmware PackageArchitecture: amd64 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-1002-oem root=UUID=ef38ac81-5316-4558-aa9d-91eb7efb1ce9
[Kernel-packages] [Bug 2073525] Re: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids
Hello Thibf, or anyone else affected, Accepted linux-firmware into noble-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20240318.git3b128b60-0ubuntu2.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- 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. ** Changed in: linux-firmware (Ubuntu Noble) Status: Confirmed => Fix Committed -- 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/2073525 Title: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids Status in The Kobuk project: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Committed Bug description: Public bug of https://bugs.launchpad.net/bugs/2073432 [ Impact ] The QAT kernel driver require those for For Sierra forest and Granite rapids hardware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx_mmp.bin [ Test Plan ] cpa_sample_code supplied with qatlib and the Linux kernel can be run to validate the firmware. [ Where problems could occur ] QAT not working on those platform. [ Other Info ] * Requested by intel, compatible on kernel since 6.4, mantic doesn't apply as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/kobuk/+bug/2073525/+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 2068001] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2068001 Title: Add support for DCN 3.5.1 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Noble: Fix Released Status in linux-firmware source package in Oracular: Fix Released Bug description: [Impact] Products with DCN 3.5.1 need linux-firmware to be added for noble. Matching kernel support is already in kernel 6.9. Without this firmware amdgpu won't bind. [Test Plan] Boot system and ensure accelerated graphics works. [Where problems could occur] This firmware is only loaded on hardware with DCN 3.5.1, VPE 6.1.1, VCN 4.0.6, SDMA 6.1.1, GC 11.5.1, PSP 14.0.1, or ISP 4.1.1 [Other info] Here are commit IDs: 7cdafcea amdgpu: Add support for DMCUB 3.5.1 df778e92 amdgpu: add support for VPE 6.1.1 bf6f3544 amdgpu: add support for VCN 4.0.6 f2f93bed amdgpu: add support for SDMA 6.1.1 dbffb07e amdgpu: add support for PSP 14.0.1 a54ce0ff amdgpu: add support for GC 11.5.1 aae82243 amdgpu: add new ISP 4.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2068001/+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 2069412] Update Released
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 encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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/2069412
Title:
CS42L43 and CS35L56 for soundwire on Intel LNL/ARL
Status in HWE Next:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Noble:
Fix Released
Status in linux-firmware source package in Oracular:
Fix Released
Bug description:
[SRU Justification]
[Impact]
Missing firmware for CS42L43 and CS35L56 for soundwire on Intel
LNL/ARL.
[Fix]
linux-firmware upstream commit 57077702373e ("linux-firmware: Add
firmware for Cirrus CS35L56 for Dell laptops").
[Test Case]
With successful loads, there should be dmesg txt showing the loaded
firmware, such as:
cs35l56 sdw:0:2:01fa:3556:01:2: DSP1:
cirrus/cs35l56-b0-dsp1-misc-10280c6b-spkid1-amp3.bin: v3.11.11
cs35l56 sdw:0:3:01fa:3556:01:0: DSP1:
cirrus/cs35l56-b0-dsp1-misc-10280c6b-spkid1-amp1.bin: v3.11.11
...
[Where problems could occur]
New hardware. No known problem yet.
[Other Info]
While this has been included in upstream tag 20240410, it's
automatically included in linux-firmware/oracular version
Ubuntu-20240730.git65c5d9b1-0ubuntu1, and therefore only Noble is
nominated for SRU.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2069412/+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 2071771] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2071771 Title: Missing firmware for Intel NPU driver on Intel Lunar Lake platform: Failed to request firmware: -2 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Noble: Fix Released Status in linux-firmware source package in Oracular: Fix Released Bug description: [Impact] Failed to load firmware for Intel NPU driver on Intel Lunar Lake platform: intel_vpu :00:0b.0: enabling device ( -> 0002) intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 intel_vpu :00:0b.0: probe with driver intel_vpu failed with error -2 [Fix] Firmware blob is publicly available as https://github.com/intel/linux- npu- driver/blob/09225e2521c01fa1101d795541259b651d6444d6/firmware/bin/vpu_40xx_v0.0.bin [Test Case] Expected dmesg: intel_vpu :00:0b.0: enabling device ( -> 0002) intel_vpu :00:0b.0: [drm] Firmware: intel/vpu/vpu_40xx_v0.0.bin, version: Jun 11 2024*LNL*ci_tag_ud202424_vpu_rc_20240611_0003*f3e8a8f27471d4127d8d92a8dc679b861ef43e43 [drm] Initialized intel_vpu 1.0.0 20230117 for :00:0b.0 on minor 0 [Where problems could occur] No. [Other Info] Nominated Noble for the next oem kernel and devel series Oracular. == original bug report == $ sudo dmesg|grep vpu [2.669659] intel_vpu :00:0b.0: enabling device ( -> 0002) [2.673377] intel_vpu :00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2 [2.673689] intel_vpu :00:0b.0: probe with driver intel_vpu failed with error -2 Intel NPU (Neural Processing Unit) driver is previously known as Intel VPU (Versatile Processing Unit). Firmware blob is publicly available as https://github.com/intel/linux- npu- driver/blob/09225e2521c01fa1101d795541259b651d6444d6/firmware/bin/vpu_40xx_v0.0.bin Expected dmesg: [2.652245] intel_vpu :00:0b.0: enabling device ( -> 0002) [2.668902] intel_vpu :00:0b.0: [drm] Firmware: intel/vpu/vpu_40xx_v0.0.bin, version: Jun 11 2024*LNL*ci_tag_ud202424_vpu_rc_20240611_0003*f3e8a8f27471d4127d8d92a8dc679b861ef43e43 [2.697292] [drm] Initialized intel_vpu 1.0.0 20230117 for :00:0b.0 on minor 0 --- ProblemType: Bug ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:ubuntu 1302 F pipewire /dev/snd/controlC0: ubuntu 1302 F pipewire ubuntu 1306 F wireplumber CRDA: N/A CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.hotfix.squashfs ./boot/grub/grub.cfg CasperMD5CheckResult: fail Dependencies: firmware-sof-signed 2023.12.1-1ubuntu1+exp.4 [origin: unknown] DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for Dell # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-noble-oem-24.04b-edge-20240621-7 DistroRelease: Ubuntu 24.04 InstallationDate: Installed on 2024-06-21 (12 days ago) InstallationMedia: Ubuntu OEM 24.04 LTS "Noble Numbat" - Release amd64 (20240619) IwConfig: lono wireless extensions. enx00e04c6a23a4 no wireless extensions. MachineType: Dell Inc. XPS 13 9350 Package: linux-firmware 20240318.git3b128b60-0ubuntu2.1+exp.3 [origin: unknown] PackageArchitecture: amd64 ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.10.0-1005-oem root=UUID=a9a37260-b46f-4821-b711-37314ef9e3ed ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.10.0-1005.5-oem 6.10.0-rc4 RelatedPackageVersions: linux-restricted-modules-6.10.0-1005-oem N/A linux-backports-modules-6.10.0-1005-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.1+exp.3 RfKill: Tags: noble third-party-packages Uname: Linux 6.10.0-1005-oem x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably
[Kernel-packages] [Bug 2073047] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2073047 Title: Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops working after a few suspend/resume cycles Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: SRU Justification: == [Impact] AX200 Bluetooth stops working after a few suspend/resume cycles. [Fix] Update the Bluetooth firmware and align with upstream. [Test] Bug reporter tested on hardware, Bluetooth works fine. [Where problems could occur] It may break Bluetooth of AX200. === After upgrading to Linux 6.8.0-38, Bluetooth adapter (USB part of the Intel AX200) stops working after a few suspend/resume cycles. WiFi (PCIe part) continues to work as expected. Kernel log shows: Bluetooth: hci0: Reading Intel version command failed (-110) instead of the usual: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 Bluetooth: hci0: Device revision is 1 Bluetooth: hci0: Secure boot is enabled Bluetooth: hci0: OTP lock is enabled Bluetooth: hci0: API lock is enabled Bluetooth: hci0: Debug lock is disabled Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi Bluetooth: hci0: Boot Address: 0x24800 Bluetooth: hci0: Firmware Version: 255-255.255 Bluetooth: hci0: Waiting for firmware download to complete Bluetooth: hci0: Firmware loaded in 2111457 usecs Bluetooth: hci0: Waiting for device to boot Bluetooth: hci0: Device booted in 14560 usecs Bluetooth: hci0: Malformed MSFT vendor event: 0x02 Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc Bluetooth: hci0: Applying Intel DDC parameters completed Bluetooth: hci0: Firmware revision 0.3 build 249 week 27 2023 Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported. Bluetooth: MGMT ver 1.22 First appeared on 6.8.0-38, 6.8.0-36 and earlier worked without issues. I suspect linux-firmware might be missing updates corresponding to changes in the kernel driver or a regression was introduced in the update. Machine: Dell XPS13-9350 Device: Intel AX200 Rev 1a (WiFi/Bluetooth combo) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2073047/+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 2071812] Update Released
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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2071812 Title: Add support for AMD ISP 4.1.1 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Noble: Fix Released Bug description: [Impact] Products with DCN 3.5.1 need linux-firmware to be added for noble. Matching kernel support will be in kernel 6.11. [Test Plan] Boot system and ensure MIPI-Camera works. [Where problems could occur] This firmware is only loaded on hardware with ISP 4.1.1 [Other info] Here are commit IDs: aae82243 amdgpu: add new ISP 4.1.1 33a95082 amdgpu: Update ISP FW for isp v4.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2071812/+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 2073047] Please test proposed package
Hello Eugene, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.33 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2073047 Title: Regression on Linux 6.8.0-38: Bluetooth adapter (Intel AX200) stops working after a few suspend/resume cycles Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Fix Released Bug description: SRU Justification: == [Impact] AX200 Bluetooth stops working after a few suspend/resume cycles. [Fix] Update the Bluetooth firmware and align with upstream. [Test] Bug reporter tested on hardware, Bluetooth works fine. [Where problems could occur] It may break Bluetooth of AX200. === After upgrading to Linux 6.8.0-38, Bluetooth adapter (USB part of the Intel AX200) stops working after a few suspend/resume cycles. WiFi (PCIe part) continues to work as expected. Kernel log shows: Bluetooth: hci0: Reading Intel version command failed (-110) instead of the usual: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 Bluetooth: hci0: Device revision is 1 Bluetooth: hci0: Secure boot is enabled Bluetooth: hci0: OTP lock is enabled Bluetooth: hci0: API lock is enabled Bluetooth: hci0: Debug lock is disabled Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi Bluetooth: hci0: Boot Address: 0x24800 Bluetooth: hci0: Firmware Version: 255-255.255 Bluetooth: hci0: Waiting for firmware download to complete Bluetooth: hci0: Firmware loaded in 2111457 usecs Bluetooth: hci0: Waiting for device to boot Bluetooth: hci0: Device booted in 14560 usecs Bluetooth: hci0: Malformed MSFT vendor event: 0x02 Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc Bluetooth: hci0: Applying Intel DDC parameters completed Bluetooth: hci0: Firmware revision 0.3 build 249 week 27 2023 Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported. Bluetooth: MGMT ver 1.22 First appeared on 6.8.0-38, 6.8.0-36 and earlier worked without issues. I suspect linux-firmware might be missing updates corresponding to changes in the kernel driver or a regression was introduced in the update. Machine: Dell XPS13-9350 Device: Intel AX200 Rev 1a (WiFi/Bluetooth combo) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2073047/+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 2073525] Re: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids
Hello Thibf, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.33 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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: linux-firmware (Ubuntu Jammy) Status: Confirmed => Fix Committed -- 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/2073525 Title: [SRU]QAT: Add 402xx (CPM2.0c) firmware for Sierra forest and Granite rapids Status in The Kobuk project: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: Confirmed Bug description: Public bug of https://bugs.launchpad.net/bugs/2073432 [ Impact ] The QAT kernel driver require those for For Sierra forest and Granite rapids hardware. https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx.bin https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/qat_402xx_mmp.bin [ Test Plan ] cpa_sample_code supplied with qatlib and the Linux kernel can be run to validate the firmware. [ Where problems could occur ] QAT not working on those platform. [ Other Info ] * Requested by intel, compatible on kernel since 6.4, mantic doesn't apply as EOL. To manage notifications about this bug go to: https://bugs.launchpad.net/kobuk/+bug/2073525/+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 2073108] Please test proposed package
Hello 何思亮, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.33 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2073108 Title: Failed to detect Wireless LAN device Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/2073108 [Impact] ath10k loaded firmware ath10k/QCA6174/hw3.0 with error [Fix] Update FW binary to the latest for ath10k/QCA6174/hw3.0 [Test Case] 1. Install 5.15.0-116.126-generic kernel with ath10k driver enabled. 2. Install the linux-firmware with latest ath10k/QCA6174/hw3.0 firmware 3. Run checkbox test case com.canonical.certification::wireless/detect. [Where problems could occur] New firmware is only loaded by the QCA6174 with hw 3.0, we haven't tested the device with hw 2.0. --- udev failed to detect wireless LAN at 5.15.0-116.126-generic. It was passed at 5.15.0-115.125-generic. terminal log: ubuntu@dell-precision-5530-c26342:~$ nmcli device status DEVICE TYPE STATE CONNECTION enx00e04c68fef9 ethernet connected netplan-enx00e04c68fef9 lo loopback unmanaged -- ubuntu@dell-precision-5530-c26342:~$ iw dev ubuntu@dell-precision-5530-c26342:~$ ls /sys/class/net | grep wl ubuntu@dell-precision-5530-c26342:~$ checkbox log: ---[ Detect if at least one Wireless LAN device is detected ]--- ID: com.canonical.certification::wireless/detect Category: Wireless networking tests No devices detected by udev Outcome: job failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-116-generic 5.15.0-116.126 ProcVersionSignature: Ubuntu 5.15.0-116.126-generic 5.15.158 Uname: Linux 5.15.0-116-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1108 F pulseaudio CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/) CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. Date: Mon Jul 15 05:45:08 2024 InstallationDate: Installed on 2022-05-10 (796 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enx00e04c68fef9 no wireless extensions. MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-116-generic root=UUID=8390b3ba-ff2e-4b3f-9828-f7e201e8c536 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-116-generic N/A linux-backports-modules-5.15.0-116-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.31 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This
[Kernel-packages] [Bug 2077296] Re: Add more region support of QCOM WiFi WCN7850
Hello AaronMa, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.33 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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: linux-firmware (Ubuntu Jammy) Status: New => Fix Committed -- 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/2077296 Title: Add more region support of QCOM WiFi WCN7850 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: Fix Committed Status in linux-firmware source package in Noble: New Status in linux-firmware source package in Oracular: New Bug description: [Impact] Qualcomm WiFi chip WCN7850 needs new board-2.bin for more regions. [Fix] Update board-2.bin in linux-firmware. [Test] Boot up, and WiFi works fine. [Where problems could occur] It may break Qualcomm WiFi WCN7850. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2077296/+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 2076180] Please test proposed package
Hello Juerg, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.33 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2076180 Title: Add new firmwares for 6.8 hwe kernel Status in linux-firmware package in Ubuntu: Triaged Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] The 6.8 HWE kernel requires firmware that is not (yet) provided by linux-firmware in Jammy. This obviously results in non-functional HW components. [Fix] Add missing firmware blobs and links. [Test Case] Ideally: Verify that the 6.8 kernel loads the new firmware blobs and the affected HW components function as expected. Realistically: Mostly untestable due to lack of availability of relevant HW. [Where Problems Could Occur] This adds only new firmware blobs (and symbolic links) that the 5.15 GA kernel doesn't care about so should not introduce any issues. In case that's an incorrect assumption, some HW components might not function properly if the new blobs are incompatible with the 5.15 GA kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2076180/+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 2077490] Please test proposed package
Hello Kevin, or anyone else affected, Accepted linux-firmware into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/20220329.git681281e4-0ubuntu3.33 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- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. 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 linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2077490 Title: Error: out of memory while booting after installing the linux-firmware in proposed Status in initramfs-tools package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] I found that there are some machines in cert lab can't boot after installing the linux-frimware in proposed with 6.8.0-40 kernel. After selecting booting with the 6.8.0-40 kernel, it shows error: out of memory on the screen then freeze. There aren't any journal logs available, since they froze at very early stage. Following are the machines got impacted for now https://certification.canonical.com/hardware/202306-31695/ https://certification.canonical.com/hardware/202306-31696/ Problem details: The linux-firmware package provides new (gigantic) firmware blobs and symlinks to directories that contain those. initramfs-tools can't handle the directory symlinks and puts multiple copies of the same blobs into the initrd blowing it up to a size where it becomes problematic on some machines. [Test Case] Verify the affected machine boots again with the updated firmware package. Install updated linux-firmware package and confirm that there are no duplicate firmware files in /lib/firmware and inside the initrd. Also verify that there are no broken symlinks. [Where Problems Could Occur] If the new symlinks are broken, we end up with drivers not finding their firmwares which results in non-functional HW components. [Notes] This is not a general solution for the problem of the ever growing size of the initrd. It just alleviate it some. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2077490/+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 2077145] Re: GDS force mitigation re-enabled in 6.10 (and 6.11) causing crashes
applied, will be in -5.5 (the real one)
** Changed in: linux (Ubuntu)
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.launchpad.net/bugs/2077145
Title:
GDS force mitigation re-enabled in 6.10 (and 6.11) causing crashes
Status in linux package in Ubuntu:
In Progress
Bug description:
The (supposedly unintended) re-enabling of GDS force migration in the
Ubuntu 6.10 kernels causes the AVX instruction to be disabled on older
CPUs which have no available microcode update. This causes various
programs to crash due to the unconditional use of AVX in libgnutls.so,
libxul.so, etc.
Typically "traps" of "invalid opcode" will be seen in dmesg output
along with the initial notice:
[0.121833] GDS: Microcode update needed! Disabling AVX as mitigation.
[0.121835] GDS: Mitigation: AVX disabled, no microcode
When GDS force mitigation appeared in the kernel, with default "y", it
created a lot of issues like these and Ubuntu quickly patched all
their kernels, this from the 6.2.0-28.29_6.2.0-31.31 diff:
==
```
diff -u linux-6.2.0/debian.master/changelog
linux-6.2.0/debian.master/changelog
--- linux-6.2.0/debian.master/changelog
+++ linux-6.2.0/debian.master/changelog
@@ -1,3 +1,13 @@
+linux (6.2.0-31.31) lunar; urgency=medium
+
+ * lunar/linux: 6.2.0-31.31 -proposed tracker (LP: #2031146)
+
+ * libgnutls report "trap invalid opcode" when trying to install packages
over
+https (LP: #2031093)
+- [Config]: disable CONFIG_GDS_FORCE_MITIGATION
+
+ -- Thadeu Lima de Souza Cascardo Mon, 14 Aug 2023
08:29:52 -0300
+
linux (6.2.0-28.29) lunar; urgency=medium
* lunar/linux: 6.2.0-28.29 -proposed tracker (LP: #2030547)
diff -u linux-6.2.0/debian.master/config/annotations
linux-6.2.0/debian.master/config/annotations
--- linux-6.2.0/debian.master/config/annotations
+++ linux-6.2.0/debian.master/config/annotations
@@ -4992,7 +4992,7 @@
CONFIG_GCC_VERSION policy<{'amd64': '120200',
'arm64': '120200', 'armhf': '120200', 'ppc64el': '120200', 'riscv64': '120200',
's390x': '120200'}>
CONFIG_GCOV_KERNEL policy<{'amd64': 'n',
'arm64': 'n', 'armhf': 'n', 'ppc64el': 'n', 'riscv64': 'n', 's390x': 'n'}>
CONFIG_GDB_SCRIPTS policy<{'amd64': 'y',
'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y', 's390x': 'y'}>
-CONFIG_GDS_FORCE_MITIGATION policy<{'amd64': 'y'}>
+CONFIG_GDS_FORCE_MITIGATION policy<{'amd64': 'n'}>
CONFIG_GEMINI_ETHERNET policy<{'arm64': 'm',
'armhf': 'm', 'ppc64el': 'm', 'riscv64': 'm'}>
CONFIG_GENERIC_ADC_BATTERY policy<{'amd64': 'm',
'arm64': 'm', 'armhf': 'm', 'ppc64el': 'm', 'riscv64': 'm'}>
CONFIG_GENERIC_ADC_THERMAL policy<{'amd64': 'm',
'arm64': 'm', 'armhf': 'm', 'ppc64el': 'm', 'riscv64': 'm'}>
```
==
In upstream 6.9 the option was renamed from
CONFIG_GDS_FORCE_MITIGATION to CONFIG_MITIGATION_GDS_FORCE, but when
Ubuntu jumped from 6.8 to 6.10, this customization was lost, seen in
the 6.8.0-31.31_6.10.0-15.15 diff:
==
```
CONFIG_GDB_SCRIPTS policy<{'amd64': 'y',
'arm64': 'y', 'armhf': 'y', 'ppc64el': 'y', 'riscv64': 'y', 's390x': 'y'}>
-CONFIG_GDS_FORCE_MITIGATION policy<{'amd64': 'n'}>
CONFIG_GEMINI_ETHERNET policy<{'arm64': 'm',
'armhf': 'm', 'ppc64el': 'm', 'riscv64': 'm'}>
...
CONFIG_MITIGATE_SPECTRE_BRANCH_HISTORY policy<{'arm64': 'y'}>
+CONFIG_MITIGATION_CALL_DEPTH_TRACKING policy<{'amd64': 'y'}>
+CONFIG_MITIGATION_GDS_FORCE policy<{'amd64': 'y'}>
+CONFIG_MITIGATION_IBPB_ENTRYpolicy<{'amd64': 'y'}>
+CONFIG_MITIGATION_IBRS_ENTRYpolicy<{'amd64': 'y'}>
```
==
I am sure this was an oversight, and that the old option was simply
dropped because it didn't exist any longer, without thinking of it
being renamed (among a lot of other renames).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077145/+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 2077540] Re: [24.10] Please test secure-boot and lockdown on the 6.11 kernel (s390x) for Oracular
thanks! -- 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/2077540 Title: [24.10] Please test secure-boot and lockdown on the 6.11 kernel (s390x) for Oracular Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: The Canonical kernel team is working on a new 6.11 kernel for 'oracular' (24.10) and has an early build ready for secure-boot and lockdown testing (version 6.11.0-4.4). To avoid potentially negative implications that a broken secure-boot lockdown functionality would cause (esp. using the production key), we ask to get secure-boot tested early in the cycle using Canonical kernel team's PPA key for signature. The early test build is available at: ppa:canonical-kernel-team/unstable (https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/) The PPA key used for signing can be found in the tarball available here: https://ppa.launchpad.net/canonical-kernel-team/unstable/ubuntu/dists/devel/main/signed/linux-generate-unstable-s390x/current/ (Please note that this kernel is coming from the 'canonical-kernel- team' PPA, hence it is NOT signed with the regular archive/release/production key, instead with the above PPA's key!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077540/+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 2077490] Re: Error: out of memory while booting after installing the linux-firmware in proposed
the initramfs-tools bug about handling symlinked directories got fixed yesterday in 0.144 :) -- 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/2077490 Title: Error: out of memory while booting after installing the linux-firmware in proposed Status in initramfs-tools package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Confirmed Bug description: [Impact] I found that there are some machines in cert lab can't boot after installing the linux-frimware in proposed with 6.8.0-40 kernel. After selecting booting with the 6.8.0-40 kernel, it shows error: out of memory on the screen then freeze. There aren't any journal logs available, since they froze at very early stage. Following are the machines got impacted for now https://certification.canonical.com/hardware/202306-31695/ https://certification.canonical.com/hardware/202306-31696/ Problem details: The linux-firmware package provides new (gigantic) firmware blobs and symlinks to directories that contain those. initramfs-tools can't handle the directory symlinks and puts multiple copies of the same blobs into the initrd blowing it up to a size where it becomes problematic on some machines. [Test Case] Verify the affected machine boots again with the updated firmware package. Install updated linux-firmware package and confirm that there are no duplicate firmware files in /lib/firmware and inside the initrd. Also verify that there are no broken symlinks. [Where Problems Could Occur] If the new symlinks are broken, we end up with drivers not finding their firmwares which results in non-functional HW components. [Notes] This is not a general solution for the problem of the ever growing size of the initrd. It just alleviate it some. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2077490/+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 2077490] Re: Error: out of memory while booting after installing the linux-firmware in proposed
I wonder if simpledrm also works in cases like when the only display is attached to the dGPU on a hybrid system. But yeah, this is something to test. -- 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/2077490 Title: Error: out of memory while booting after installing the linux-firmware in proposed Status in initramfs-tools package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Confirmed Bug description: [Impact] I found that there are some machines in cert lab can't boot after installing the linux-frimware in proposed with 6.8.0-40 kernel. After selecting booting with the 6.8.0-40 kernel, it shows error: out of memory on the screen then freeze. There aren't any journal logs available, since they froze at very early stage. Following are the machines got impacted for now https://certification.canonical.com/hardware/202306-31695/ https://certification.canonical.com/hardware/202306-31696/ Problem details: The linux-firmware package provides new (gigantic) firmware blobs and symlinks to directories that contain those. initramfs-tools can't handle the directory symlinks and puts multiple copies of the same blobs into the initrd blowing it up to a size where it becomes problematic on some machines. [Test Case] Verify the affected machine boots again with the updated firmware package. Install updated linux-firmware package and confirm that there are no duplicate firmware files in /lib/firmware and inside the initrd. Also verify that there are no broken symlinks. [Where Problems Could Occur] If the new symlinks are broken, we end up with drivers not finding their firmwares which results in non-functional HW components. [Notes] This is not a general solution for the problem of the ever growing size of the initrd. It just alleviate it some. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2077490/+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 2077490] Re: Error: out of memory while booting after installing the linux-firmware in proposed
and there's this https://airlied.blogspot.com/2023/04/kernel-module-firmware-selection- for.html -- 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/2077490 Title: Error: out of memory while booting after installing the linux-firmware in proposed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I found that there are some machines in cert lab can't boot after installing the linux-frimware in proposed with 6.8.0-40 kernel. After selecting booting with the 6.8.0-40 kernel, it shows error: out of memory on the screen then freeze. There aren't any journal logs available, since they froze at very early stage. Following are the machines got impacted for now https://certification.canonical.com/hardware/202306-31695/ https://certification.canonical.com/hardware/202306-31696/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2077490/+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 2077490] Re: Error: out of memory while booting after installing the linux-firmware in proposed
arch had the same issue, but using different tools it seems https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/issues/238 ** Bug watch added: gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/issues #238 https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/issues/238 -- 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/2077490 Title: Error: out of memory while booting after installing the linux-firmware in proposed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: I found that there are some machines in cert lab can't boot after installing the linux-frimware in proposed with 6.8.0-40 kernel. After selecting booting with the 6.8.0-40 kernel, it shows error: out of memory on the screen then freeze. There aren't any journal logs available, since they froze at very early stage. Following are the machines got impacted for now https://certification.canonical.com/hardware/202306-31695/ https://certification.canonical.com/hardware/202306-31696/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2077490/+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 2077490] Re: Error: out of memory while booting after installing the linux-firmware in proposed
the whole nvidia dir is only 63MB on the git tree, so maybe the initramfs tools are a bit shit -- 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/2077490 Title: Error: out of memory while booting after installing the linux-firmware in proposed Status in initramfs-tools package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: I found that there are some machines in cert lab can't boot after installing the linux-frimware in proposed with 6.8.0-40 kernel. After selecting booting with the 6.8.0-40 kernel, it shows error: out of memory on the screen then freeze. There aren't any journal logs available, since they froze at very early stage. Following are the machines got impacted for now https://certification.canonical.com/hardware/202306-31695/ https://certification.canonical.com/hardware/202306-31696/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2077490/+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 2077540] [NEW] [24.10] Please test secure-boot and lockdown on the 6.11 kernel (s390x) for Oracular
Public bug reported: The Canonical kernel team is working on a new 6.11 kernel for 'oracular' (24.10) and has an early build ready for secure-boot and lockdown testing (version 6.11.0-4.4). To avoid potentially negative implications that a broken secure-boot lockdown functionality would cause (esp. using the production key), we ask to get secure-boot tested early in the cycle using Canonical kernel team's PPA key for signature. The early test build is available at: ppa:canonical-kernel-team/unstable (https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/) The PPA key used for signing can be found in the tarball available here: https://ppa.launchpad.net/canonical-kernel-team/unstable/ubuntu/dists/devel/main/signed/linux-generate-unstable-s390x/current/ (Please note that this kernel is coming from the 'canonical-kernel-team' PPA, hence it is NOT signed with the regular archive/release/production key, instead with the above PPA's key!) ** Affects: ubuntu-z-systems Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-z-systems 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/2077540 Title: [24.10] Please test secure-boot and lockdown on the 6.11 kernel (s390x) for Oracular Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: The Canonical kernel team is working on a new 6.11 kernel for 'oracular' (24.10) and has an early build ready for secure-boot and lockdown testing (version 6.11.0-4.4). To avoid potentially negative implications that a broken secure-boot lockdown functionality would cause (esp. using the production key), we ask to get secure-boot tested early in the cycle using Canonical kernel team's PPA key for signature. The early test build is available at: ppa:canonical-kernel-team/unstable (https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable/) The PPA key used for signing can be found in the tarball available here: https://ppa.launchpad.net/canonical-kernel-team/unstable/ubuntu/dists/devel/main/signed/linux-generate-unstable-s390x/current/ (Please note that this kernel is coming from the 'canonical-kernel- team' PPA, hence it is NOT signed with the regular archive/release/production key, instead with the above PPA's key!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2077540/+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
