[Bug 2139322] Re: Fix conntrack use after free when ovs hardware offload is enabled

This bug is awaiting verification that the linux/6.8.0-110.110 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-noble-linux' to 'verification-done-noble-linux'. If
the problem still exists, change the tag 'verification-needed-noble-
linux' to 'verification-failed-noble-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-v2 verification-needed-noble-linux

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139322

Title:
Fix conntrack use after free when ovs hardware offload is enabled

Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Committed

Bug description:
[Impact]

Enable mlx5 ovs hardware offload on 6.8 kernel, we see different issues on our production environment,
it only happens under real and heavy workloads.

Issue 1, general protection fault:

[75202.650580] general protection fault, probably for non-canonical address 0x9cad655f9b42c237: 0000 [#1] PREEMPT SMP NOPTI
[75202.661464] CPU: 29 PID: 0 Comm: swapper/29 Kdump: loaded Not tainted 6.8.0-51-generic #52~22.04.1-Ubuntu
[75202.671039] Hardware name: Dell Inc. PowerEdge R7525/0H3K7P, BIOS 2.15.2 04/02/2024
[75202.678701] RIP: 0010:kmalloc_trace+0xd7/0x360
[75202.683158] Code: 83 78 10 00 48 8b 38 0f 84 36 02 00 00 48 85 ff 0f 84 2d 02 00 00 41 8b 44 24 28 49 8b 9c 24 b8 00 00 00 49 8b 34 24 48 01 f8 <48> 33 18 48 89 c1 48 89 f8 48 0f c9 48 31 cb 48 8d 8a 00 20 00 00
[75202.701933] RSP: 0018:ffffabfc19a08990 EFLAGS: 00010282
[75202.707166] RAX: 9cad655f9b42c237 RBX: 1c00e25717636e48 RCX: 0000000000000000
[75202.714310] RDX: 000000bec1e5c01d RSI: 000000000003b980 RDI: 9cad655f9b42c1b7
[75202.721449] RBP: ffffabfc19a089e0 R08: 0000000000000000 R09: 0000000000000000
[75202.728593] R10: ffffabfc19a08a00 R11: 0000000000000000 R12: ffff94db00050c00
[75202.735735] R13: 0000000000000920 R14: 00000000000000d8 R15: 0000000000000000
[75202.742876] FS: 0000000000000000(0000) GS:ffff95da7cc80000(0000) knlGS:0000000000000000
[75202.750971] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[75202.756722] CR2: 00007a5f6af90010 CR3: 0000010263b44002 CR4: 0000000000f70ef0
[75202.763866] PKRU: 55555554
[75202.766581] Call Trace:
[75202.769033] <IRQ>
[75202.771053] ? show_regs+0x6d/0x80
[75202.774483] ? die_addr+0x37/0xa0
[75202.777807] ? exc_general_protection+0x1db/0x480
[75202.782525] ? asm_exc_general_protection+0x27/0x30
[75202.787412] ? kmalloc_trace+0xd7/0x360
[75202.791261] ? flow_offload_alloc+0x64/0x120 [nf_flow_table]
[75202.796938] flow_offload_alloc+0x64/0x120 [nf_flow_table]
[75202.802431] ? nf_conntrack_in+0x113/0x360 [nf_conntrack]
[75202.807846] ? flow_offload_alloc+0x64/0x120 [nf_flow_table]
[75202.813517] tcf_ct_flow_table_process_conn+0xc2/0x1e0 [act_ct]
[75202.819444] tcf_ct_act+0x6c8/0xae0 [act_ct]
[75202.823726] tcf_action_exec+0xbc/0x190
[75202.827571] __tcf_classify+0xcb/0x1f0
[75202.831332] tcf_classify+0xff/0x260
[75202.834920] tc_run+0xa3/0x110
[75202.837987] __netif_receive_skb_core.constprop.0+0x459/0xf90
[75202.843744] ? dev_gro_receive+0xc0/0x350
[75202.847763] ? srso_alias_return_thunk+0x5/0xfbef5
[75202.852565] ? napi_gro_receive+0x73/0x220
[75202.856675] __netif_receive_skb_list_core+0xfd/0x250
[75202.861736] netif_receive_skb_list_internal+0x1a3/0x2d0
[75202.867056] ? srso_alias_return_thunk+0x5/0xfbef5
[75202.871858] ? mlx5e_rx_cq_process_basic_cqe_comp+0x2f7/0x310 [mlx5_core]
[75202.878752] napi_complete_done+0x74/0x1c0
[75202.882855] mlx5e_napi_poll+0x190/0x7b0 [mlx5_core]
[75202.887911] __napi_poll+0x33/0x200
[75202.891753] net_rx_action+0x181/0x2e0
[75202.895849] handle_softirqs+0xdb/0x340
[75202.900027] __irq_exit_rcu+0xd9/0x100
[75202.904103] irq_exit_rcu+0xe/0x20
[75202.907828] common_interrupt+0xa4/0xb0
[75202.911983] </IRQ>
[75202.914387] <TASK>
[75202.916786] asm_common_interrupt+0x27/0x40
[75202.921258] RIP: 0010:mwait_idle+0x50/0x80

This is caused by use-after-free in slab (kmalloc-256).

Issue 2, soft lockup:

[148720.717134] watchdog: BUG: soft lockup - CPU#3 stuck for 7923s! [swapper/3:0]
[148720.725207] Modules linked in: act_csum act_pedit act_tunnel_key vhost_net vhost tap vfio_pci vfio_pci_core vfio_iommu_type1 vfio iommufd xt_CT xt_tcpudp nft_compat nf_tables veth
act_ct nf_flow_table nf_conntrack_netlink nvme_fabrics nvme_keyring xfs dm_crypt act_skbedit act_vlan act_mirred cls_matchall geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnet
link act_gact cls_flower sch_ingress openvswitch nsh nf_conncount nf_nat 8021q garp mrp stp llc bonding sunrpc binfmt_misc nls_iso8859_1 mlx5_vdpa vringh vhost_iotlb vdpa intel_rapl_ms
r intel_rapl_common amd64_edac edac_mce_amd kvm_amd kvm irqbypass rapl dell_wmi video ledtrig_audio sparse_keymap dell_smbios dcdbas dell_wmi_descriptor wmi_bmof ipmi_ssif ccp ptdma k1
0temp acpi_power_meter ipmi_si acpi_ipmi ipmi_devintf ipmi_msghandler mac_hid dm_service_time sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr efi_pstore ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov
[148720.725328] async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c mlx5_ib ib_uverbs macsec ib_core ses enclosure raid1 raid0 bcache mlx5_core crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic ghash_clmulni_intel mlxfw mpt3sas sha256_ssse3 nvme psample ahci sha1_ssse3 raid_class tg3 nvme_core tls libahci xhci_pci mgag200 nvme_auth scsi_transport_sas i2c_algo_bit pci_hyperv_intf i2c_piix4 xhci_pci_renesas wmi aesni_intel crypto_simd cryptd
[148720.725385] CPU: 3 PID: 0 Comm: swapper/3 Kdump: loaded Tainted: G L 6.8.0-57-generic #59~22.04.1-Ubuntu
[148720.725388] Hardware name: Dell Inc. PowerEdge R7525/0H3K7P, BIOS 2.16.3 09/10/2024
[148720.725390] RIP: 0010:flow_offload_hash_cmp+0x1f/0x40 [nf_flow_table]
[148720.725398] Code: 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 8b 47 08 ba 32 00 00 00 48 8d 7e 08 48 89 c6 48 89 e5 e8 62 4a b6 fa 5d <85> c0 0f 95 c0 0f b6 c0 31 d2 31 f6 31 ff e9 b9 3b ee fa 66 66 2e
[148720.725401] RSP: 0018:ffffad9f403fc928 EFLAGS: 00000246
[148720.725404] RAX: 0000000000000004 RBX: ffff8a8f9a3c3a40 RCX: 0000000000000000
[148720.725406] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[148720.725409] RBP: ffffad9f403fc990 R08: 0000000000000000 R09: 000000000000003c
[148720.725411] R10: 000000000000003c R11: 0000000000000000 R12: ffff89b49b080000
[148720.725413] R13: 0000000000000000 R14: ffff89b49b09e6b8 R15: ffff89b2ba69ea58
[148720.725415] FS: 0000000000000000(0000) GS:ffff8a8f3bf80000(0000) knlGS:0000000000000000
[148720.725417] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[148720.725419] CR2: 000056c0ae793900 CR3: 000000021d904002 CR4: 0000000000f70ef0
[148720.725421] PKRU: 55555554
[148720.725423] Call Trace:
[148720.725426] <IRQ>
[148720.725428] ? show_regs+0x6d/0x80
[148720.725435] ? watchdog_timer_fn+0x206/0x290
[148720.725441] ? __pfx_watchdog_timer_fn+0x10/0x10
[148720.725445] ? __hrtimer_run_queues+0x112/0x2a0
[148720.725450] ? srso_alias_return_thunk+0x5/0xfbef5
[148720.725457] ? hrtimer_interrupt+0xf6/0x250
[148720.725462] ? __sysvec_apic_timer_interrupt+0x51/0x120
[148720.725467] ? sysvec_apic_timer_interrupt+0x3b/0xd0
[148720.725473] ? asm_sysvec_apic_timer_interrupt+0x1b/0x20
[148720.725479] ? flow_offload_hash_cmp+0x1f/0x40 [nf_flow_table]
[148720.725484] ? flow_offload_lookup+0xb2/0x180 [nf_flow_table]
[148720.725491] tcf_ct_flow_table_lookup.isra.0+0x244/0x6b0 [act_ct]
[148720.725494] ? srso_alias_return_thunk+0x5/0xfbef5
[148720.725499] ? ovs_dp_process_packet+0x1af/0x220 [openvswitch]
[148720.725518] tcf_ct_act+0x23d/0xae0 [act_ct]
[148720.725524] tcf_action_exec+0xbc/0x190
[148720.725531] __tcf_classify+0xcb/0x1f0
[148720.725535] tcf_classify+0xff/0x260
[148720.725539] tc_run+0xa3/0x110
[148720.725543] ? srso_alias_return_thunk+0x5/0xfbef5
[148720.725547] __netif_receive_skb_core.constprop.0+0x459/0xf90
[148720.725552] ? dev_gro_receive+0x150/0x350
[148720.725557] ? srso_alias_return_thunk+0x5/0xfbef5
[148720.725560] ? napi_gro_receive+0x73/0x220
[148720.725564] __netif_receive_skb_list_core+0xfd/0x250
[148720.725569] netif_receive_skb_list_internal+0x1a3/0x2d0
[148720.725573] ? srso_alias_return_thunk+0x5/0xfbef5
[148720.725578] ? mlx5e_rx_cq_process_basic_cqe_comp+0x2f7/0x310 [mlx5_core]
[148720.725688] napi_complete_done+0x74/0x1c0
[148720.725693] mlx5e_napi_poll+0x190/0x7b0 [mlx5_core]
[148720.725782] __napi_poll+0x33/0x200
[148720.725786] net_rx_action+0x181/0x2e0
[148720.725792] handle_softirqs+0xdb/0x340
[148720.725799] __irq_exit_rcu+0xd9/0x100
[148720.725802] irq_exit_rcu+0xe/0x20

before soft lockup, we see some error messages from mlx5, e.g.:

[486111.016058] mlx5_core 0000:41:00.1 ens3f1: NETDEV WATCHDOG: CPU: 119: transmit queue 0 timed out 17547 ms
[486111.025773] mlx5_core 0000:41:00.1 ens3f1: TX timeout detected
[486111.031726] mlx5_core 0000:41:00.1 ens3f1: TX timeout on queue: 0, SQ: 0x11d0, CQ: 0x1487, SQ Cons: 0xae7a SQ Prod: 0xaec3, usecs since last trans: 17562000
[486111.045845] mlx5_core 0000:41:00.1 ens3f1: EQ 0x7: Cons = 0x8ac57014, irqn = 0x5f5

Kernel cmdline:
GRUB_CMDLINE_LINUX_DEFAULT="console=tty0 console=ttyS0,115200n8 nvme_core.multipath=0 amd_iommu=on iommu=pt probe_vf=0 transparent_hugepage=never hugepagesz=1G hugepages=1536 default_hugepagesz=1G"

[Fix]

This upstream commit fixes it:

commit 03428ca5cee9f0792edc996c06ce4514816af1fb
Author: Florian Westphal <fw@strlen.de>
Date: Tue Jan 14 00:50:36 2025 +0100

    netfilter: conntrack: rework offload nf_conn timeout extension
logic

And a dependency:

commit 31768596b15aa8c9c55f078acad29d0238c8269b
Author: Florian Westphal <fw@strlen.de>
Date: Tue Jan 14 00:50:35 2025 +0100

    netfilter: conntrack: remove skb argument from nf_ct_refresh

The 2 patches fix ct use-after-free and packet gets stuck issues,
which should be related to the above two call traces.

[Test Plan]

This issue can only be reproduced on PS6 with mlx5 NIC and ovs hw-offload enabled.
We have run test kernel with these 2 patches for 3 weeks, it's been working fine.

[Where problems could occur]

The patch makes sure to take a refcount on ct and test offload bits, it could prevent ct being used after it's removed.
And also modifies flow offload teardown logic, if there is anything wrong, the ovs flow offload might be broken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139322/+subscriptions

[Bug 2141276] Re: efi: Fix swapped arguments to bsearch() in efi_status_to_*() SAUCE patch

This bug is awaiting verification that the linux/6.8.0-110.110 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-noble-linux' to 'verification-done-noble-linux'. If
the problem still exists, change the tag 'verification-needed-noble-
linux' to 'verification-failed-noble-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-v2 verification-needed-noble-linux

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141276

Title:
efi: Fix swapped arguments to bsearch() in efi_status_to_*() SAUCE
patch

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 Questing:
Fix Committed
Status in linux source package in Resolute:
Fix Released

Bug description:

[Impact]
The swapped bsearch() arguments cause the function to calculate incorrect
element offsets when searching the efi_error_codes array:

- Buggy behavior: bsearch thinks there are 24 elements of 12 bytes each
- Correct behavior: 12 elements of 24 bytes each (on 64-bit systems)

This causes efi_status_to_err() and efi_status_to_str() to read at wrong
memory offsets (every 12 bytes instead of every 24 bytes), potentially:
- Returning incorrect errno values for EFI status codes
- Returning wrong error description strings
- Failing to find valid status codes and returning default error values

These functions are used to translate EFI firmware error codes to Linux
errno values and human-readable strings, affecting error reporting for
EFI-related operations including secure boot and firmware variable access.

[Test Plan]
1. Build kernel with the fix applied
2. Boot system with UEFI firmware
3. Trigger EFI error conditions that exercise efi_status_to_err() and
efi_status_to_str(), such as:
- Secure boot signature verification failures
- EFI variable access errors
- MOK (Machine Owner Key) operations
4. Verify dmesg shows correct EFI error messages
5. Compare error messages before and after the fix to confirm correct
status code translation

Alternatively, a unit test can verify the bsearch returns correct results:
- Call efi_status_to_err() with known EFI status codes (e.g., EFI_SUCCESS,
EFI_INVALID_PARAMETER, EFI_SECURITY_VIOLATION)
- Verify correct errno values are returned (-EINVAL, -EACCES, etc.)

[Where problems could occur]
The fix swaps two adjacent function arguments. Potential issues:

1. The fix changes the search behavior, which could theoretically expose
latent bugs in code that was accidentally working due to the incorrect
search. For example, if code was relying on the -EINVAL fallback when
bsearch failed to find a match, it might now receive a different (correct)
errno value.

2. Since this affects EFI error reporting, any issues would manifest as
incorrect error messages in dmesg or wrong return values from EFI
operations. This could affect debugging but should not cause system
instability.

[Other Info]
- Root cause: The bug was introduced in the SAUCE patch cherry-picked from
kernel-ark commit 2ae9082db0b5:
https://gitlab.com/cki-project/kernel-ark/-/commit/2ae9082db0b5
- Upstream fix: https://gitlab.com/cki-project/kernel-ark/-/commit/49bcc48074ba
- bsearch(3) man page: https://man7.org/linux/man-pages/man3/bsearch.3.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141276/+subscriptions

[Bug 2142235] Re: linux-riscv-6.8 is FTBFS because of missing patches

This bug is awaiting verification that the linux/6.8.0-110.110 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-noble-linux' to 'verification-done-noble-linux'. If
the problem still exists, change the tag 'verification-needed-noble-
linux' to 'verification-failed-noble-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-v2 verification-needed-noble-linux

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142235

Title:
linux-riscv-6.8 is FTBFS because of missing patches

Status in linux package in Ubuntu:
Invalid
Status in linux-riscv-6.8 package in Ubuntu:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-riscv-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Committed
Status in linux-riscv-6.8 source package in Noble:
Invalid

Bug description:
[ Impact ]

Previously applied patches to the generic kernel are making
jammy:linux-riscv-6.8 FTBFS because of missing declaration of some
functions in arch/riscv/net/bpf_jit.h.

Those previous patches were applied in bulk as part of upstream stable patchset 2026-01-26.
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139072

The following commit, fixing CVE-2025-40079, from kernel 6.12, uses functions that were not yet defined in 6.8:
 riscv, bpf: Sign extend struct ops return values properly (fd2e08128944a7679e753f920e9eda72057e427c)

Error log:
/build/jammy/arch/riscv/net/bpf_jit_comp64.c:582:17: error: implicit declaration of function 'emit_sextb'; did you mean 'emit_sub'? [-Werror=implicit-function-declaration]
/build/jammy/arch/riscv/net/bpf_jit_comp64.c:585:17: error: implicit declaration of function 'emit_sexth'; did you mean 'emit_zext_32'? [-Werror=implicit-function-declaration]
/build/jammy/arch/riscv/net/bpf_jit_comp64.c:588:17: error: implicit declaration of function 'emit_sextw'; did you mean 'emit_subw'? [-Werror=implicit-function-declaration]
... and more missing functions

[ Fix ]

Cherry picked 6 missing commits from upstream:
- e33758f7493c9ad8cf6960bcf7c70f5761f3acfb "riscv, bpf: Unify 32-bit sign-extension to emit_sextw"
- 914c7a5ff18a225f7df254ae3433574f3d47b711 "riscv, bpf: Unify 32-bit zero-extension to emit_zextw"
- - 361db44c3c59cde05e9926647f16255e274a37f4 "riscv, bpf: Simplify sext and zext logics in branch instructions"
- 647b93f65daa128d9a0e4aac744a5fcf5f58b2d2 "riscv, bpf: Add necessary Zbb instructions"
- 519fb722bea09ae2664ad21f8ef4360fb799eb2f "riscv, bpf: Optimize sign-extention mov insns with Zbb support"
- 06a33d024838414432b6c0f51f994e7f1695b74f "riscv, bpf: Optimize bswap insns with Zbb support"

Those commits add definitions for the missing functions emit_sextX and
others.

[ Test Case ]

Kernel build succeeded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142235/+subscriptions

[Bug 2142337] Re: Coresight fails to build on 6.8.0-102 due to missing function and arg definitions

This bug is awaiting verification that the linux/6.8.0-110.110 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-noble-linux' to 'verification-done-noble-linux'. If
the problem still exists, change the tag 'verification-needed-noble-
linux' to 'verification-failed-noble-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-v2 verification-needed-noble-linux

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142337

Title:
Coresight fails to build on 6.8.0-102 due to missing function and arg
definitions

Status in linux package in Ubuntu:
New
Status in linux-nvidia package in Ubuntu:
Invalid
Status in linux-nvidia-6.8 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-nvidia source package in Jammy:
Invalid
Status in linux-nvidia-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Committed
Status in linux-nvidia source package in Noble:
Fix Released
Status in linux-nvidia-6.8 source package in Noble:
Invalid

Bug description:
SRU Justification:

[Impact]

When CONFIG_CORESIGHT is enabled, noble 6.8.0-102 fails to build with
the following errors:

```
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_init':
drivers/hwtracing/coresight/coresight-catu.c:728:15: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
728 | ret = coresight_init_driver("catu", &catu_driver, &catu_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-catu.c: In function 'catu_exit':
drivers/hwtracing/coresight/coresight-catu.c:736:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
736 | coresight_remove_driver(&catu_driver, &catu_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~~~
| coresight_remove_links
...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function '__tmc_probe':
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: error: 'id' undeclared (first use in this function); did you mean 'fd'?
500 | coresight_get_uci_data(id));
| ^~
| fd
drivers/hwtracing/coresight/coresight-tmc-core.c:500:65: note: each undeclared identifier is reported only once for each function it appears in
...
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_init':
drivers/hwtracing/coresight/coresight-tmc-core.c:728:16: error: implicit declaration of function 'coresight_init_driver' [-Werror=implicit-function-declaration]
728 | return coresight_init_driver("tmc", &tmc_driver, &tmc_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~
drivers/hwtracing/coresight/coresight-tmc-core.c: In function 'tmc_exit':
drivers/hwtracing/coresight/coresight-tmc-core.c:733:9: error: implicit declaration of function 'coresight_remove_driver'; did you mean 'coresight_remove_links'? [-Werror=implicit-function-declaration]
733 | coresight_remove_driver(&tmc_driver, &tmc_platform_driver);
| ^~~~~~~~~~~~~~~~~~~~~~~
| coresight_remove_links
...
drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_enable':
drivers/hwtracing/coresight/coresight-tpdm.c:299:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
299 | if (!coresight_take_mode(csdev, mode)) {
| ^~~~~~~~~~~~~~~~~~~
| coresight_make_links
drivers/hwtracing/coresight/coresight-tpdm.c: In function 'tpdm_disable':
drivers/hwtracing/coresight/coresight-tpdm.c:345:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
345 | coresight_set_mode(csdev, CS_MODE_DISABLED);
| ^~~~~~~~~~~~~~~~~~
| coresight_get_pid
drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_enable':
drivers/hwtracing/coresight/coresight-dummy.c:26:14: error: implicit declaration of function 'coresight_take_mode'; did you mean 'coresight_make_links'? [-Werror=implicit-function-declaration]
26 | if (!coresight_take_mode(csdev, mode))
| ^~~~~~~~~~~~~~~~~~~
| coresight_make_links
drivers/hwtracing/coresight/coresight-dummy.c: In function 'dummy_source_disable':
drivers/hwtracing/coresight/coresight-dummy.c:37:9: error: implicit declaration of function 'coresight_set_mode'; did you mean 'coresight_get_pid'? [-Werror=implicit-function-declaration]
37 | coresight_set_mode(csdev, CS_MODE_DISABLED);
| ^~~~~~~~~~~~~~~~~~
| coresight_get_pid
```

These errors are a result of including the following patches in
upstream stable updates, but missing some dependencies from the
original patch sets:

Error description: __tmc_probe:id not defined
Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
Missing commit: 852e9a32058a ("coresight: stm: Extract device name from AMBA pid based table lookup")
3ab210297c31 ("coresight: tmc: Extract device properties from AMBA pid based table lookup")
Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
(https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)

Error description: catu,tmc: coresight_{init,remove}_driver not defined
Break commit: n/linux aaf260b9572e ("coresight: tmc: Move ACPI support from AMBA driver to platform driver")
n/linux cf08211db65c ("coresight: catu: Move ACPI support from AMBA driver to platform driver")
Missing commit: 075b7cd7ad7d ("coresight: Add helpers registering/removing both AMBA and platform drivers")
Patch series: "coresight: Move remaining AMBA ACPI devices into platform driver"
(https://lists-ec2.linaro.org/archives/list/coresight@lists.linaro.org/thread/XGJAJMHSDE5P7YSX33CIW5DHKR6C343L/)

Error description: tpdm,dummy: coresight_{set,take}_mode not defined
Break commit: n/linux f30974e15e66 ("Coresight: Set correct cs_mode for TPDM to fix disable issue")
n/linux e76e67682488 ("Coresight: Set correct cs_mode for dummy source to fix disable issue")
Missing commit: d724f65218b9 ("coresight: Add helper for atomically taking the device")
Patch series: "coresight: Separate sysfs and Perf usage and some other cleanups"
(https://lists.infradead.org/pipermail/linux-arm-kernel/2024-January/899269.html)

[Fix]

Revert the break commits.

[Test Plan]

Ensure CONFIG_CORESIGHT and CONFIG_CORESIGHT_CATU are enabled, then
compile test.

[Where problems could occur]

These reverts are technically removing fixes from the tree, which have the
potential to cause behaviour changes or regressions. However, the generic
kernel has never been able to build these coresight features, and thus we have
not observed any examples of the issue the patches intended to fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142337/+subscriptions

[Bug 2143033] Re: ADT test for linux package failed with "fatal: unable to connect to git.launchpad.net"

This bug is awaiting verification that the linux/6.8.0-110.110 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-noble-linux' to 'verification-done-noble-linux'. If
the problem still exists, change the tag 'verification-needed-noble-
linux' to 'verification-failed-noble-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-v2 verification-needed-noble-linux

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143033

Title:
ADT test for linux package failed with "fatal: unable to connect to
git.launchpad.net"

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

Bug description:
[ Impact ]
After the prodstack migration, the newer autopkgtest runners will block
non-HTTP(S) traffic, which consequently leads to the following error when
running the ADT test for the linux package:
Cloning into 'kernel-testing'...
fatal: unable to connect to git.launchpad.net:
git.launchpad.net[0: 185.125.188.190]: errno=Connection timed out
git.launchpad.net[1: 185.125.188.189]: errno=Connection timed out

[ Test Plan ]
Run git clone on an Openstack VM, with proxy configured.
It works with https protocol but not git protocol.

[ Where problems could occur ]
As the test itself is already broken, this change won't make it any worse.
And we already have this fix in Questing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143033/+subscriptions

[Bug 2144730] Re: ITS mitigation is not enabled on affected CPUs

This bug is awaiting verification that the linux/6.8.0-110.110 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-noble-linux' to 'verification-done-noble-linux'. If
the problem still exists, change the tag 'verification-needed-noble-
linux' to 'verification-failed-noble-linux'.


If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.


See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: kernel-spammed-noble-linux-v2 verification-needed-noble-linux

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144730

Title:
ITS mitigation is not enabled on affected CPUs

Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Committed

Bug description:
SRU Justification:

[Impact]

Noble upstream stable patchset 2025-10-29 (LP :#210277) included the
following patch from upstream stable branch linux-6.12.y:

* 68d59e9ba3842 ("x86/its: Enable Indirect Target Selection
mitigation")

The patch disables ITS mitigation if CONFIG_MITIGATION_RETPOLINE or
CONFIG_MITIGATION_RETHUNK are not available:

+ if (!IS_ENABLED(CONFIG_MITIGATION_RETPOLINE) ||
+ !IS_ENABLED(CONFIG_MITIGATION_RETHUNK)) {
+ pr_err("WARNING: ITS mitigation depends on retpoline and rethunk support\n");
+ its_mitigation = ITS_MITIGATION_OFF;
+ goto out;
+ }

However, while linux-6.12.y contains the following two commits, Noble
does not:

* aefb2f2e619b6 ("x86/bugs: Rename CONFIG_RETPOLINE => CONFIG_MITIGATION_RETPOLINE")
* 0911b8c52c4d6 ("x86/bugs: Rename CONFIG_RETHUNK => CONFIG_MITIGATION_RETHUNK")

This discrepancy will cause the runtime check from above to always fail
in Noble, since the config options have not been renamed and therefore
are undefined, even though we have both CONFIG_RETPOLINE and
CONFIG_RETHUNK enabled through annotations. Consequently, ITS mitigation
will not be enabled when it should be.

On affected CPUs this will cause the kernel to warn about missing ITS
mitigation:

[ 0.966659] ITS: WARNING: ITS mitigation depends on retpoline and rethunk support
[ 0.966851] ITS: Vulnerable

[Fix]

Backport the patches that rename CONFIG_RETPOLINE and CONFIG_RETHUNK to
Noble:

* aefb2f2e619b6 ("x86/bugs: Rename CONFIG_RETPOLINE => CONFIG_MITIGATION_RETPOLINE")
* 0911b8c52c4d6 ("x86/bugs: Rename CONFIG_RETHUNK => CONFIG_MITIGATION_RETHUNK")

[Test Plan]

Boot on an affected CPU and check that ITS mitigation is enabled as
expected:

[ 3.642521] active return thunk: its_return_thunk
[ 3.643523] ITS: Mitigation: Aligned branch/return thunks

[Where problems could occur]

Any present or future patch that relies on the old naming scheme for the
two options will behave as if the features are unavailable which could
cause critical mitigations to be either less effective or disabled
completely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144730/+subscriptions

[Bug 2116169] Re: Support Intel Scorpius Peak, Whale Peak WiFi/Bluetooth for Intel Panther Lake platforms

** Description changed:

[ SRU Justification: kernel ]

[ Impact ]

Missing device ID for Intel Scorpius Peak on Intel Panther Lake H-484
variant platforms.

Fix is commit 04efaba1d7615 ("Bluetooth: btintel_pcie: Add id of
Scorpious, Panther Lake-H484") from linux-next.

[ Test Plan ]

1. Install kernels from proposed pocket:
   ```
   $ sudo apt-get install --no-install-recommends --yes linux-oem-24.04d
   ```
   At this moment you also need unreleased-yet linux-firmware blobs from ppa:canonical-hwe-team/linux-firmware-staging to verify.

2. Check dmesg for successful firmware loading:
   ```
   Bluetooth: hci0: Waiting for firmware download to complete
   Bluetooth: hci0: Firmware loaded in 438953 usecs
   Bluetooth: hci0: Waiting for device to boot
   Bluetooth: hci0: Device booted in 32278 usecs
   Bluetooth: hci0: Waiting for device transition to d0
   Bluetooth: hci0: Device moved to D0 in 47 usecs
   Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-00a0-0291-pci.ddc
   Bluetooth: hci0: Applying Intel DDC parameters completed
   Bluetooth: hci0: Firmware timestamp 2025.37 buildtype 1 build 63418
   Bluetooth: hci0: Firmware SHA1: 0xf7618b6b
   Bluetooth: hci0: Fseq status: Success (0x00)
   Bluetooth: hci0: Fseq executed: 00.98.00.08
   Bluetooth: hci0: Fseq BT Top: 00.98.00.08
   ```

3. Check device availability:
   ```
   $ btmgmt info
   Index list with 1 item
   hci0: Primary controller
           addr 4C:B0:4A:FB:3C:3A version 13 manufacturer 2 class 0x6c010c
           ...
   ```

[ Where problems could occur ]

New hardware support on new platforms. No regression, but might have
stability problems.

[ Other Info ]

Intel Panther Lake is to be supported by 6.17+ kernels. Nominate linux-
oem-6.17/noble and linux/questing, linux/resolute, and linux-
unstable/resolute.

========== original bug report ==========

* WhP2/SpP2 (ES2)
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-wh-a0.pnvm
      - iwlwifi-sc-a0-wh-a0-99.ucode
    * BT (IOSF):
      - ibt-00a0-00a1-iml.sfi
      - ibt-00a0-00a1-pci.ddc
      - ibt-00a0-00a1-pci.sfi
  * PV
    * BT (IOSF):
      - ibt-00a0-00a1-iml.sfi
      - ibt-00a0-00a1-pci.ddc
      - ibt-00a0-00a1-pci.sfi
* WhP2/SpP2 (QS)
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-wh-b0.pnvm
      - iwlwifi-sc-a0-wh-b0-99.ucode
  * PV
    * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4b245479aacaba0e3b073c31151b711e7aae1268, bug 2136987
      - iwlwifi-sc-a0-wh-b0.pnvm
      - iwlwifi-sc-a0-wh-b0-101.ucode
    * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
      - ibt-00a0-01a1-iml.sfi
      - ibt-00a0-01a1-pci.ddc
      - ibt-00a0-01a1-pci.sfi
* GfP2
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-gf-a0.pnvm
      - iwlwifi-sc-a0-gf-a0-99.ucode
    * BT (IOSF):
      - ibt-00a0-0041-iml.sfi
      - ibt-00a0-0041-pci.ddc
      - ibt-00a0-0041-pci.sfi
  * PV
    * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=41b492fc74644827ee5b816ca97324e2ff9e627a, bug 2136987
      - iwlwifi-sc-a0-gf-a0.pnvm
      - iwlwifi-sc-a0-gf-a0-100.ucode
    * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f383a26428bfbf9e2cd2445aba8b7de4dafc308c, bug 2136804
      - ibt-00a0-0041-iml.sfi
      - ibt-00a0-0041-pci.ddc
      - ibt-00a0-0041-pci.sfi
* FmP2
  * WiFi:
    - iwlwifi-gl-c0-fm-c0-c102.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=9a9285ce9b440c4d0d6d9aeff181615d8052dfe7, bug 2146301
    - iwlwifi-sc-a0-fm-c0-c101.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=0a041632c1564a6acf6d2b9ab7cbc64474a2c323, bug 2146301
  * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
    - ibt-00a0-0291-iml.sfi
    - ibt-00a0-0291-pci.sfi
    - ibt-00a0-0291-pci.ddc

Device IDs
* BE211 (WhP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_41108086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_00118086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_41108086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_00118086
* BE213 (SpP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_43148086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_01118086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_43148086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_01118086
* AX211 (GfP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_40908086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_00008086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_40908086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_00008086
- * BE201 (BE201)
+ * BE201 (FmP2)

[Panther Lake]

* Whale Peak2
  - WiFi: iwlwifi-sc-a0-wh-b0, iwlwifi-sc-a0-wh-b0
  - BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}

* Scorpius Peak2
  - WiFi: iwlwifi-sc-a0-wh-a0, iwlwifi-sc-a0-wh-b0
  - BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}

* GfP2
  - WiFi: iwlwifi-sc-a0-gf-a0
  - BT: ibt-00a0-0041-{iml.sfi,pci.sfi,pci.ddc}

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2116169

Title:
Support Intel Scorpius Peak, Whale Peak WiFi/Bluetooth for Intel
Panther Lake platforms

Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Incomplete
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-firmware source package in Noble:
Incomplete
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-firmware source package in Questing:
Incomplete
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-firmware source package in Resolute:
Incomplete
Status in linux-oem-6.17 source package in Resolute:
Invalid

Bug description:
[ SRU Justification: kernel ]

[ Impact ]

Missing device ID for Intel Scorpius Peak on Intel Panther Lake H-484
variant platforms.

Fix is commit 04efaba1d7615 ("Bluetooth: btintel_pcie: Add id of
Scorpious, Panther Lake-H484") from linux-next.

[ Test Plan ]

1. Install kernels from proposed pocket:
   ```
   $ sudo apt-get install --no-install-recommends --yes linux-oem-24.04d
   ```
   At this moment you also need unreleased-yet linux-firmware blobs from ppa:canonical-hwe-team/linux-firmware-staging to verify.

2. Check dmesg for successful firmware loading:
   ```
   Bluetooth: hci0: Waiting for firmware download to complete
   Bluetooth: hci0: Firmware loaded in 438953 usecs
   Bluetooth: hci0: Waiting for device to boot
   Bluetooth: hci0: Device booted in 32278 usecs
   Bluetooth: hci0: Waiting for device transition to d0
   Bluetooth: hci0: Device moved to D0 in 47 usecs
   Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-00a0-0291-pci.ddc
   Bluetooth: hci0: Applying Intel DDC parameters completed
   Bluetooth: hci0: Firmware timestamp 2025.37 buildtype 1 build 63418
   Bluetooth: hci0: Firmware SHA1: 0xf7618b6b
   Bluetooth: hci0: Fseq status: Success (0x00)
   Bluetooth: hci0: Fseq executed: 00.98.00.08
   Bluetooth: hci0: Fseq BT Top: 00.98.00.08
   ```

3. Check device availability:
   ```
   $ btmgmt info
   Index list with 1 item
   hci0: Primary controller
           addr 4C:B0:4A:FB:3C:3A version 13 manufacturer 2 class 0x6c010c
           ...
   ```

[ Where problems could occur ]

New hardware support on new platforms. No regression, but might have
stability problems.

[ Other Info ]

Intel Panther Lake is to be supported by 6.17+ kernels. Nominate
linux-oem-6.17/noble and linux/questing, linux/resolute, and linux-
unstable/resolute.

========== original bug report ==========

* WhP2/SpP2 (ES2)
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-wh-a0.pnvm
      - iwlwifi-sc-a0-wh-a0-99.ucode
    * BT (IOSF):
      - ibt-00a0-00a1-iml.sfi
      - ibt-00a0-00a1-pci.ddc
      - ibt-00a0-00a1-pci.sfi
  * PV
    * BT (IOSF):
      - ibt-00a0-00a1-iml.sfi
      - ibt-00a0-00a1-pci.ddc
      - ibt-00a0-00a1-pci.sfi
* WhP2/SpP2 (QS)
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-wh-b0.pnvm
      - iwlwifi-sc-a0-wh-b0-99.ucode
  * PV
    * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4b245479aacaba0e3b073c31151b711e7aae1268, bug 2136987
      - iwlwifi-sc-a0-wh-b0.pnvm
      - iwlwifi-sc-a0-wh-b0-101.ucode
    * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
      - ibt-00a0-01a1-iml.sfi
      - ibt-00a0-01a1-pci.ddc
      - ibt-00a0-01a1-pci.sfi
* GfP2
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-gf-a0.pnvm
      - iwlwifi-sc-a0-gf-a0-99.ucode
    * BT (IOSF):
      - ibt-00a0-0041-iml.sfi
      - ibt-00a0-0041-pci.ddc
      - ibt-00a0-0041-pci.sfi
  * PV
    * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=41b492fc74644827ee5b816ca97324e2ff9e627a, bug 2136987
      - iwlwifi-sc-a0-gf-a0.pnvm
      - iwlwifi-sc-a0-gf-a0-100.ucode
    * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f383a26428bfbf9e2cd2445aba8b7de4dafc308c, bug 2136804
      - ibt-00a0-0041-iml.sfi
      - ibt-00a0-0041-pci.ddc
      - ibt-00a0-0041-pci.sfi
* FmP2
  * WiFi:
    - iwlwifi-gl-c0-fm-c0-c102.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=9a9285ce9b440c4d0d6d9aeff181615d8052dfe7, bug 2146301
    - iwlwifi-sc-a0-fm-c0-c101.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=0a041632c1564a6acf6d2b9ab7cbc64474a2c323, bug 2146301
  * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
    - ibt-00a0-0291-iml.sfi
    - ibt-00a0-0291-pci.sfi
    - ibt-00a0-0291-pci.ddc

Device IDs
* BE211 (WhP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_41108086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_00118086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_41108086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_00118086
* BE213 (SpP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_43148086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_01118086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_43148086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_01118086
* AX211 (GfP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_40908086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_00008086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_40908086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_00008086
* BE201 (FmP2)

[Panther Lake]

* Whale Peak2
  - WiFi: iwlwifi-sc-a0-wh-b0, iwlwifi-sc-a0-wh-b0
  - BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}

* Scorpius Peak2
  - WiFi: iwlwifi-sc-a0-wh-a0, iwlwifi-sc-a0-wh-b0
  - BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}

* GfP2
  - WiFi: iwlwifi-sc-a0-gf-a0
  - BT: ibt-00a0-0041-{iml.sfi,pci.sfi,pci.ddc}

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2116169/+subscriptions

[Bug 2116169] Re: Support Intel Scorpius Peak, Whale Peak WiFi/Bluetooth for Intel Panther Lake platforms

** Description changed:

[ SRU Justification: kernel ]

[ Impact ]

Missing device ID for Intel Scorpius Peak on Intel Panther Lake H-484
variant platforms.

Fix is commit 04efaba1d7615 ("Bluetooth: btintel_pcie: Add id of
Scorpious, Panther Lake-H484") from linux-next.

[ Test Plan ]

1. Install kernels from proposed pocket:
   ```
   $ sudo apt-get install --no-install-recommends --yes linux-oem-24.04d
   ```
   At this moment you also need unreleased-yet linux-firmware blobs from ppa:canonical-hwe-team/linux-firmware-staging to verify.

2. Check dmesg for successful firmware loading:
   ```
   Bluetooth: hci0: Waiting for firmware download to complete
   Bluetooth: hci0: Firmware loaded in 438953 usecs
   Bluetooth: hci0: Waiting for device to boot
   Bluetooth: hci0: Device booted in 32278 usecs
   Bluetooth: hci0: Waiting for device transition to d0
   Bluetooth: hci0: Device moved to D0 in 47 usecs
   Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-00a0-0291-pci.ddc
   Bluetooth: hci0: Applying Intel DDC parameters completed
   Bluetooth: hci0: Firmware timestamp 2025.37 buildtype 1 build 63418
   Bluetooth: hci0: Firmware SHA1: 0xf7618b6b
   Bluetooth: hci0: Fseq status: Success (0x00)
   Bluetooth: hci0: Fseq executed: 00.98.00.08
   Bluetooth: hci0: Fseq BT Top: 00.98.00.08
   ```

3. Check device availability:
   ```
   $ btmgmt info
   Index list with 1 item
   hci0: Primary controller
           addr 4C:B0:4A:FB:3C:3A version 13 manufacturer 2 class 0x6c010c
           ...
   ```

[ Where problems could occur ]

New hardware support on new platforms. No regression, but might have
stability problems.

[ Other Info ]

Intel Panther Lake is to be supported by 6.17+ kernels. Nominate linux-
oem-6.17/noble and linux/questing, linux/resolute, and linux-
unstable/resolute.

========== original bug report ==========

* WhP2/SpP2 (ES2)
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-wh-a0.pnvm
      - iwlwifi-sc-a0-wh-a0-99.ucode
    * BT (IOSF):
      - ibt-00a0-00a1-iml.sfi
      - ibt-00a0-00a1-pci.ddc
      - ibt-00a0-00a1-pci.sfi
  * PV
    * BT (IOSF):
      - ibt-00a0-00a1-iml.sfi
      - ibt-00a0-00a1-pci.ddc
      - ibt-00a0-00a1-pci.sfi
* WhP2/SpP2 (QS)
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-wh-b0.pnvm
      - iwlwifi-sc-a0-wh-b0-99.ucode
  * PV
    * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4b245479aacaba0e3b073c31151b711e7aae1268, bug 2136987
      - iwlwifi-sc-a0-wh-b0.pnvm
      - iwlwifi-sc-a0-wh-b0-101.ucode
    * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
      - ibt-00a0-01a1-iml.sfi
      - ibt-00a0-01a1-pci.ddc
      - ibt-00a0-01a1-pci.sfi
* GfP2
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-gf-a0.pnvm
      - iwlwifi-sc-a0-gf-a0-99.ucode
    * BT (IOSF):
      - ibt-00a0-0041-iml.sfi
      - ibt-00a0-0041-pci.ddc
      - ibt-00a0-0041-pci.sfi
  * PV
    * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=41b492fc74644827ee5b816ca97324e2ff9e627a, bug 2136987
      - iwlwifi-sc-a0-gf-a0.pnvm
      - iwlwifi-sc-a0-gf-a0-100.ucode
    * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f383a26428bfbf9e2cd2445aba8b7de4dafc308c, bug 2136804
      - ibt-00a0-0041-iml.sfi
      - ibt-00a0-0041-pci.ddc
      - ibt-00a0-0041-pci.sfi
* FmP2
-   * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=9a9285ce9b440c4d0d6d9aeff181615d8052dfe7
-     - iwlwifi-sc-a0-fm-c0.pnvm
-     - iwlwifi-sc-a0-fm-c0-101.ucode
+   * WiFi:
+     - iwlwifi-gl-c0-fm-c0-c102.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=9a9285ce9b440c4d0d6d9aeff181615d8052dfe7, bug 2146301
+     - iwlwifi-sc-a0-fm-c0-c101.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=0a041632c1564a6acf6d2b9ab7cbc64474a2c323, bug 2146301
  * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
    - ibt-00a0-0291-iml.sfi
    - ibt-00a0-0291-pci.sfi
    - ibt-00a0-0291-pci.ddc

Device IDs
* BE211 (WhP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_41108086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_00118086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_41108086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_00118086
* BE213 (SpP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_43148086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_01118086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_43148086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_01118086
* AX211 (GfP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_40908086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_00008086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_40908086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_00008086
* BE201 (BE201)

[Panther Lake]

* Whale Peak2
  - WiFi: iwlwifi-sc-a0-wh-b0, iwlwifi-sc-a0-wh-b0
  - BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}

* Scorpius Peak2
  - WiFi: iwlwifi-sc-a0-wh-a0, iwlwifi-sc-a0-wh-b0
  - BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}

* GfP2
  - WiFi: iwlwifi-sc-a0-gf-a0
  - BT: ibt-00a0-0041-{iml.sfi,pci.sfi,pci.ddc}

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2116169

Title:
Support Intel Scorpius Peak, Whale Peak WiFi/Bluetooth for Intel
Panther Lake platforms

Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Incomplete
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-firmware source package in Noble:
Incomplete
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-firmware source package in Questing:
Incomplete
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-firmware source package in Resolute:
Incomplete
Status in linux-oem-6.17 source package in Resolute:
Invalid

Bug description:
[ SRU Justification: kernel ]

[ Impact ]

Missing device ID for Intel Scorpius Peak on Intel Panther Lake H-484
variant platforms.

Fix is commit 04efaba1d7615 ("Bluetooth: btintel_pcie: Add id of
Scorpious, Panther Lake-H484") from linux-next.

[ Test Plan ]

1. Install kernels from proposed pocket:
   ```
   $ sudo apt-get install --no-install-recommends --yes linux-oem-24.04d
   ```
   At this moment you also need unreleased-yet linux-firmware blobs from ppa:canonical-hwe-team/linux-firmware-staging to verify.

2. Check dmesg for successful firmware loading:
   ```
   Bluetooth: hci0: Waiting for firmware download to complete
   Bluetooth: hci0: Firmware loaded in 438953 usecs
   Bluetooth: hci0: Waiting for device to boot
   Bluetooth: hci0: Device booted in 32278 usecs
   Bluetooth: hci0: Waiting for device transition to d0
   Bluetooth: hci0: Device moved to D0 in 47 usecs
   Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-00a0-0291-pci.ddc
   Bluetooth: hci0: Applying Intel DDC parameters completed
   Bluetooth: hci0: Firmware timestamp 2025.37 buildtype 1 build 63418
   Bluetooth: hci0: Firmware SHA1: 0xf7618b6b
   Bluetooth: hci0: Fseq status: Success (0x00)
   Bluetooth: hci0: Fseq executed: 00.98.00.08
   Bluetooth: hci0: Fseq BT Top: 00.98.00.08
   ```

3. Check device availability:
   ```
   $ btmgmt info
   Index list with 1 item
   hci0: Primary controller
           addr 4C:B0:4A:FB:3C:3A version 13 manufacturer 2 class 0x6c010c
           ...
   ```

[ Where problems could occur ]

New hardware support on new platforms. No regression, but might have
stability problems.

[ Other Info ]

Intel Panther Lake is to be supported by 6.17+ kernels. Nominate
linux-oem-6.17/noble and linux/questing, linux/resolute, and linux-
unstable/resolute.

========== original bug report ==========

* WhP2/SpP2 (ES2)
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-wh-a0.pnvm
      - iwlwifi-sc-a0-wh-a0-99.ucode
    * BT (IOSF):
      - ibt-00a0-00a1-iml.sfi
      - ibt-00a0-00a1-pci.ddc
      - ibt-00a0-00a1-pci.sfi
  * PV
    * BT (IOSF):
      - ibt-00a0-00a1-iml.sfi
      - ibt-00a0-00a1-pci.ddc
      - ibt-00a0-00a1-pci.sfi
* WhP2/SpP2 (QS)
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-wh-b0.pnvm
      - iwlwifi-sc-a0-wh-b0-99.ucode
  * PV
    * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4b245479aacaba0e3b073c31151b711e7aae1268, bug 2136987
      - iwlwifi-sc-a0-wh-b0.pnvm
      - iwlwifi-sc-a0-wh-b0-101.ucode
    * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
      - ibt-00a0-01a1-iml.sfi
      - ibt-00a0-01a1-pci.ddc
      - ibt-00a0-01a1-pci.sfi
* GfP2
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-gf-a0.pnvm
      - iwlwifi-sc-a0-gf-a0-99.ucode
    * BT (IOSF):
      - ibt-00a0-0041-iml.sfi
      - ibt-00a0-0041-pci.ddc
      - ibt-00a0-0041-pci.sfi
  * PV
    * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=41b492fc74644827ee5b816ca97324e2ff9e627a, bug 2136987
      - iwlwifi-sc-a0-gf-a0.pnvm
      - iwlwifi-sc-a0-gf-a0-100.ucode
    * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f383a26428bfbf9e2cd2445aba8b7de4dafc308c, bug 2136804
      - ibt-00a0-0041-iml.sfi
      - ibt-00a0-0041-pci.ddc
      - ibt-00a0-0041-pci.sfi
* FmP2
  * WiFi:
    - iwlwifi-gl-c0-fm-c0-c102.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=9a9285ce9b440c4d0d6d9aeff181615d8052dfe7, bug 2146301
    - iwlwifi-sc-a0-fm-c0-c101.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=0a041632c1564a6acf6d2b9ab7cbc64474a2c323, bug 2146301
  * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
    - ibt-00a0-0291-iml.sfi
    - ibt-00a0-0291-pci.sfi
    - ibt-00a0-0291-pci.ddc

Device IDs
* BE211 (WhP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_41108086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_00118086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_41108086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_00118086
* BE213 (SpP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_43148086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_01118086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_43148086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_01118086
* AX211 (GfP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_40908086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_00008086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_40908086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_00008086
* BE201 (FmP2)

[Panther Lake]

* Whale Peak2
  - WiFi: iwlwifi-sc-a0-wh-b0, iwlwifi-sc-a0-wh-b0
  - BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}

* Scorpius Peak2
  - WiFi: iwlwifi-sc-a0-wh-a0, iwlwifi-sc-a0-wh-b0
  - BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}

* GfP2
  - WiFi: iwlwifi-sc-a0-gf-a0
  - BT: ibt-00a0-0041-{iml.sfi,pci.sfi,pci.ddc}

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2116169/+subscriptions

[Bug 2116169] Re: Support Intel Scorpius Peak, Whale Peak WiFi/Bluetooth for Intel Panther Lake platforms

** Description changed:

[ SRU Justification: kernel ]

[ Impact ]

Missing device ID for Intel Scorpius Peak on Intel Panther Lake H-484
variant platforms.

Fix is commit 04efaba1d7615 ("Bluetooth: btintel_pcie: Add id of
Scorpious, Panther Lake-H484") from linux-next.

[ Test Plan ]

1. Install kernels from proposed pocket:
   ```
   $ sudo apt-get install --no-install-recommends --yes linux-oem-24.04d
   ```
   At this moment you also need unreleased-yet linux-firmware blobs from ppa:canonical-hwe-team/linux-firmware-staging to verify.

2. Check dmesg for successful firmware loading:
   ```
   Bluetooth: hci0: Waiting for firmware download to complete
   Bluetooth: hci0: Firmware loaded in 438953 usecs
   Bluetooth: hci0: Waiting for device to boot
   Bluetooth: hci0: Device booted in 32278 usecs
   Bluetooth: hci0: Waiting for device transition to d0
   Bluetooth: hci0: Device moved to D0 in 47 usecs
   Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-00a0-0291-pci.ddc
   Bluetooth: hci0: Applying Intel DDC parameters completed
   Bluetooth: hci0: Firmware timestamp 2025.37 buildtype 1 build 63418
   Bluetooth: hci0: Firmware SHA1: 0xf7618b6b
   Bluetooth: hci0: Fseq status: Success (0x00)
   Bluetooth: hci0: Fseq executed: 00.98.00.08
   Bluetooth: hci0: Fseq BT Top: 00.98.00.08
   ```

3. Check device availability:
   ```
   $ btmgmt info
   Index list with 1 item
   hci0: Primary controller
           addr 4C:B0:4A:FB:3C:3A version 13 manufacturer 2 class 0x6c010c
           ...
   ```

[ Where problems could occur ]

New hardware support on new platforms. No regression, but might have
stability problems.

[ Other Info ]

Intel Panther Lake is to be supported by 6.17+ kernels. Nominate linux-
oem-6.17/noble and linux/questing, linux/resolute, and linux-
unstable/resolute.

========== original bug report ==========

* WhP2/SpP2 (ES2)
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-wh-a0.pnvm
      - iwlwifi-sc-a0-wh-a0-99.ucode
    * BT (IOSF):
      - ibt-00a0-00a1-iml.sfi
      - ibt-00a0-00a1-pci.ddc
      - ibt-00a0-00a1-pci.sfi
  * PV
    * BT (IOSF):
      - ibt-00a0-00a1-iml.sfi
      - ibt-00a0-00a1-pci.ddc
      - ibt-00a0-00a1-pci.sfi
* WhP2/SpP2 (QS)
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-wh-b0.pnvm
      - iwlwifi-sc-a0-wh-b0-99.ucode
  * PV
    * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4b245479aacaba0e3b073c31151b711e7aae1268, bug 2136987
      - iwlwifi-sc-a0-wh-b0.pnvm
      - iwlwifi-sc-a0-wh-b0-101.ucode
    * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
      - ibt-00a0-01a1-iml.sfi
      - ibt-00a0-01a1-pci.ddc
      - ibt-00a0-01a1-pci.sfi
* GfP2
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-gf-a0.pnvm
      - iwlwifi-sc-a0-gf-a0-99.ucode
    * BT (IOSF):
      - ibt-00a0-0041-iml.sfi
      - ibt-00a0-0041-pci.ddc
      - ibt-00a0-0041-pci.sfi
  * PV
    * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=41b492fc74644827ee5b816ca97324e2ff9e627a, bug 2136987
      - iwlwifi-sc-a0-gf-a0.pnvm
      - iwlwifi-sc-a0-gf-a0-100.ucode
    * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f383a26428bfbf9e2cd2445aba8b7de4dafc308c, bug 2136804
      - ibt-00a0-0041-iml.sfi
      - ibt-00a0-0041-pci.ddc
      - ibt-00a0-0041-pci.sfi
* FmP2
-   * WiFi:
-     - iwlwifi-sc-a0-fm-c0-c101.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=0a041632c1564a6acf6d2b9ab7cbc64474a2c323
-     - iwlwifi-sc-a0-fm-c0-c102.ucode: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=9a9285ce9b440c4d0d6d9aeff181615d8052dfe7
+   * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=9a9285ce9b440c4d0d6d9aeff181615d8052dfe7
+     - iwlwifi-sc-a0-fm-c0.pnvm
+     - iwlwifi-sc-a0-fm-c0-101.ucode
  * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
    - ibt-00a0-0291-iml.sfi
    - ibt-00a0-0291-pci.sfi
    - ibt-00a0-0291-pci.ddc

Device IDs
* BE211 (WhP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_41108086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_00118086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_41108086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_00118086
* BE213 (SpP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_43148086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_01118086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_43148086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_01118086
* AX211 (GfP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_40908086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_00008086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_40908086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_00008086
+ * BE201 (BE201)

[Panther Lake]

* Whale Peak2
  - WiFi: iwlwifi-sc-a0-wh-b0, iwlwifi-sc-a0-wh-b0
  - BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}

* Scorpius Peak2
  - WiFi: iwlwifi-sc-a0-wh-a0, iwlwifi-sc-a0-wh-b0
  - BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}

* GfP2
  - WiFi: iwlwifi-sc-a0-gf-a0
  - BT: ibt-00a0-0041-{iml.sfi,pci.sfi,pci.ddc}

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2116169

Title:
Support Intel Scorpius Peak, Whale Peak WiFi/Bluetooth for Intel
Panther Lake platforms

Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Incomplete
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-firmware source package in Noble:
Incomplete
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux-firmware source package in Questing:
Incomplete
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-firmware source package in Resolute:
Incomplete
Status in linux-oem-6.17 source package in Resolute:
Invalid

Bug description:
[ SRU Justification: kernel ]

[ Impact ]

Missing device ID for Intel Scorpius Peak on Intel Panther Lake H-484
variant platforms.

Fix is commit 04efaba1d7615 ("Bluetooth: btintel_pcie: Add id of
Scorpious, Panther Lake-H484") from linux-next.

[ Test Plan ]

1. Install kernels from proposed pocket:
   ```
   $ sudo apt-get install --no-install-recommends --yes linux-oem-24.04d
   ```
   At this moment you also need unreleased-yet linux-firmware blobs from ppa:canonical-hwe-team/linux-firmware-staging to verify.

2. Check dmesg for successful firmware loading:
   ```
   Bluetooth: hci0: Waiting for firmware download to complete
   Bluetooth: hci0: Firmware loaded in 438953 usecs
   Bluetooth: hci0: Waiting for device to boot
   Bluetooth: hci0: Device booted in 32278 usecs
   Bluetooth: hci0: Waiting for device transition to d0
   Bluetooth: hci0: Device moved to D0 in 47 usecs
   Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-00a0-0291-pci.ddc
   Bluetooth: hci0: Applying Intel DDC parameters completed
   Bluetooth: hci0: Firmware timestamp 2025.37 buildtype 1 build 63418
   Bluetooth: hci0: Firmware SHA1: 0xf7618b6b
   Bluetooth: hci0: Fseq status: Success (0x00)
   Bluetooth: hci0: Fseq executed: 00.98.00.08
   Bluetooth: hci0: Fseq BT Top: 00.98.00.08
   ```

3. Check device availability:
   ```
   $ btmgmt info
   Index list with 1 item
   hci0: Primary controller
           addr 4C:B0:4A:FB:3C:3A version 13 manufacturer 2 class 0x6c010c
           ...
   ```

[ Where problems could occur ]

New hardware support on new platforms. No regression, but might have
stability problems.

[ Other Info ]

Intel Panther Lake is to be supported by 6.17+ kernels. Nominate
linux-oem-6.17/noble and linux/questing, linux/resolute, and linux-
unstable/resolute.

========== original bug report ==========

* WhP2/SpP2 (ES2)
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-wh-a0.pnvm
      - iwlwifi-sc-a0-wh-a0-99.ucode
    * BT (IOSF):
      - ibt-00a0-00a1-iml.sfi
      - ibt-00a0-00a1-pci.ddc
      - ibt-00a0-00a1-pci.sfi
  * PV
    * BT (IOSF):
      - ibt-00a0-00a1-iml.sfi
      - ibt-00a0-00a1-pci.ddc
      - ibt-00a0-00a1-pci.sfi
* WhP2/SpP2 (QS)
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-wh-b0.pnvm
      - iwlwifi-sc-a0-wh-b0-99.ucode
  * PV
    * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=4b245479aacaba0e3b073c31151b711e7aae1268, bug 2136987
      - iwlwifi-sc-a0-wh-b0.pnvm
      - iwlwifi-sc-a0-wh-b0-101.ucode
    * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
      - ibt-00a0-01a1-iml.sfi
      - ibt-00a0-01a1-pci.ddc
      - ibt-00a0-01a1-pci.sfi
* GfP2
  * Beta
    * WiFi:
      - iwlwifi-sc-a0-gf-a0.pnvm
      - iwlwifi-sc-a0-gf-a0-99.ucode
    * BT (IOSF):
      - ibt-00a0-0041-iml.sfi
      - ibt-00a0-0041-pci.ddc
      - ibt-00a0-0041-pci.sfi
  * PV
    * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=41b492fc74644827ee5b816ca97324e2ff9e627a, bug 2136987
      - iwlwifi-sc-a0-gf-a0.pnvm
      - iwlwifi-sc-a0-gf-a0-100.ucode
    * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f383a26428bfbf9e2cd2445aba8b7de4dafc308c, bug 2136804
      - ibt-00a0-0041-iml.sfi
      - ibt-00a0-0041-pci.ddc
      - ibt-00a0-0041-pci.sfi
* FmP2
  * WiFi: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=9a9285ce9b440c4d0d6d9aeff181615d8052dfe7
    - iwlwifi-sc-a0-fm-c0.pnvm
    - iwlwifi-sc-a0-fm-c0-101.ucode
  * BT (IOSF): https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea830f7f03e37a6d5975e7796d6e9bb57f, bug 2136804
    - ibt-00a0-0291-iml.sfi
    - ibt-00a0-0291-pci.sfi
    - ibt-00a0-0291-pci.ddc

Device IDs
* BE211 (WhP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_41108086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_00118086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_41108086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_00118086
* BE213 (SpP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_43148086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_01118086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_43148086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_01118086
* AX211 (GfP2)
  * PTL-P/U (H12X/H404)
    * Wi-Fi: PCI\VEN_8086&DEV_E440&SUBSYS_40908086
    * BT: PCI\VEN_8086&DEV_E476&SUBSYS_00008086
  * PTL-H (H484)
    * Wi-Fi: PCI\VEN_8086&DEV_E340&SUBSYS_40908086
    * BT: PCI\VEN_8086&DEV_E376&SUBSYS_00008086
* BE201 (BE201)

[Panther Lake]

* Whale Peak2
  - WiFi: iwlwifi-sc-a0-wh-b0, iwlwifi-sc-a0-wh-b0
  - BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}

* Scorpius Peak2
  - WiFi: iwlwifi-sc-a0-wh-a0, iwlwifi-sc-a0-wh-b0
  - BT: ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc}

* GfP2
  - WiFi: iwlwifi-sc-a0-gf-a0
  - BT: ibt-00a0-0041-{iml.sfi,pci.sfi,pci.ddc}

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2116169/+subscriptions