[РЕШЕНО] Ошибка № ...

среда

[Bug 2065369] Re: veth.sh from ubuntu_kselftests_net failed on J-5.15 / N-6.8 (with xdp attached - gro flag)

This bug is awaiting verification that the linux-azure/5.15.0-1109.118
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-jammy-linux-azure' to 'verification-done-jammy-
linux-azure'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-azure' to 'verification-failed-jammy-linux-azure'.

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-jammy-linux-azure-v2 verification-needed-jammy-linux-azure

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

Title:
veth.sh from ubuntu_kselftests_net failed on J-5.15 / N-6.8 (with xdp
attached - gro flag)

Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Committed

Bug description:
[ Impact ]

The test veth.sh from ubuntu_kselftests_net fails on both Jammy and Noble.
...
bad setting: reducing RX nr below peer TX with XDP set ok
with xdp attached - gro flag fail - expected on found off
        - peer gro flag ok
        - tso flag ok
        - peer tso flag ok
        - aggregation fail - got 10 packets, expected 1
        - after dev off, flag fail - expected on found off
        - peer flag ok
...

The test execution reveals a consistent failure pattern
during the interaction between XDP program attachment and GRO
feature state management on veth interfaces.

It is possible to notice that the commit
d7db7775ea2e (net: veth: do not manipulate GRO when using XDP)
changed the veth driver's behavior by removing automatic GRO manipulation
when XDP programs attach or detach.
Both Noble and Jammy includes this behavioral change,
but the kselftest net:vet.sh has not been update accordingly.
In practice, commit ba5a6476e386 (selftests: net: veth: test the ability
to independently manipulate GRO and XDP) it's missing.
This creates a mismatch between actual kernel behavior and test expectations.

[ Fix ]

Backport commit ba5a6476e386 (selftests: net: veth: test the ability
to independently manipulate GRO and XDP) from mainline.

[ Test ]

Execute net:vet.sh on both Noble and Jammy.

In Noble:
$ uname -a
Linux ubuntu-noble-amd64-server 6.8.0-91-generic #92-Ubuntu SMP PREEMPT_DYNAMIC Fri Nov 28 16:26:35 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
$ sudo apt install -y build-essential docutils-common ethtool iptables jq kernel-wedge libfuse-dev libnuma-dev libssl-dev net-tools pkg-config tcpdump uuid-runtime socat netsniff-ng libcap-dev libelf-dev clang llvm
$ fakeroot debian/rules clean
$ make -j$(nproc) headers
$ sudo make run_tests -C tools/testing/selftests/net TEST_PROGS=veth.sh
# selftests: net: veth.sh
# default - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - aggregation ok
# - aggregation with TSO off ok
# with gro on - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - aggregation with TSO off ok
# gro vs xdp while down - gro flag off ok
# - after down ok
# - after xdp off ok
# - after up ok
# - after peer xdp ok
# gro vs xdp while down - gro flag on ok
# - after down ok
# - after xdp off ok
# - after up ok
# - after peer xdp ok
# default channels ok
# with gro enabled on link down - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - aggregation with TSO off ok
# setting tx channels ok
# setting both rx and tx channels ok
# bad setting: combined channels ok
# setting invalid channels nr ok
# bad setting: XDP with RX nr less than TX ok
# bad setting: reducing RX nr below peer TX with XDP set ok
# bad setting: increasing peer TX nr above RX with XDP set ok
# setting invalid channels nr ok
# with xdp attached - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - no aggregation ok
# - gro flag with GRO on ok
# - aggregation ok
# - after dev off, flag ok
# - peer flag ok
# - after gro on xdp off, gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# decreasing tx channels with device down ok
# - aggregation ok
# increasing tx channels with device down ok
# aggregation again with default and TSO off ok
ok 14 selftests: net: veth.sh

In Jammy:

$ uname -a
Linux ubuntu-jammy-amd64-server 5.15.0-163-generic #173-Ubuntu SMP Tue Oct 14 17:51:00 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
$ sudo apt install -y build-essential docutils-common ethtool iptables jq kernel-wedge libfuse-dev libnuma-dev libssl-dev net-tools pkg-config tcpdump uuid-runtime socat netsniff-ng libcap-dev libelf-dev clang llvm
$ fakeroot debian/rules clean
$ make -j$(nproc) headers
$ make -j$(nproc) -C tools/testing/selftests TARGETS=bpf SKIP_TARGETS= KDIR=/usr/src/linux-headers-5.15.0-163-generic
$ sudo make run_tests -C tools/testing/selftests/net TEST_PROGS=veth.sh
# selftests: net: veth.sh
# default - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - aggregation ok
# - aggregation with TSO off ok
# with gro on - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - aggregation with TSO off ok
# gro vs xdp while down - gro flag on ok
# - after down ok
# - after xdp off ok
# - after up ok
# - after peer xdp ok
# default channels ok
# with gro enabled on link down - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - aggregation with TSO off ok
# setting tx channels ok
# setting both rx and tx channels ok
# bad setting: combined channels ok
# setting invalid channels nr ok
# bad setting: XDP with RX nr less than TX ok
# bad setting: reducing RX nr below peer TX with XDP set ok
# bad setting: increasing peer TX nr above RX with XDP set ok
# setting invalid channels nr ok
# with xdp attached - gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# - no aggregation ok
# - gro flag with GRO on ok
# - aggregation ok
# - after dev off, flag ok
# - peer flag ok
# - after gro on xdp off, gro flag ok
# - peer gro flag ok
# - tso flag ok
# - peer tso flag ok
# decreasing tx channels with device down ok
# - aggregation ok
# increasing tx channels with device down ok
# aggregation again with default and TSO off ok
ok 7 selftests: net: veth.sh

[ Regression Potential ]

The fix affects only scripts in kselftest.
No regression potential for the kernel.

---

Issue found with Jammy 5.15.0-111.121 in sru-20240429

Reproduce rate is 100% across different arches on openstack cloud.

Test log:
ubuntu@kt-j-l-gen-5-15-bc2r4d20-u-kselftests-net-amd64:~/autotest/client/tmp/ubuntu_kselftests_net/src/linux/tools/testing/selftests/net$ sudo ./veth.sh
default - gro flag ok
        - peer gro flag ok
        - tso flag ok
        - peer tso flag ok
        - aggregation ok
        - aggregation with TSO off ok
with gro on - gro flag ok
        - peer gro flag ok
        - tso flag ok
        - peer tso flag ok
        - aggregation with TSO off ok
default channels ok
with gro enabled on link down - gro flag ok
        - peer gro flag ok
        - tso flag ok
        - peer tso flag ok
        - aggregation with TSO off ok
setting tx channels ok
bad setting: combined channels ok
setting invalid channels nr ok
bad setting: XDP with RX nr less than TX ok
bad setting: reducing RX nr below peer TX with XDP set ok
with xdp attached - gro flag fail - expected on found off
        - peer gro flag ok
        - tso flag ok
        - peer tso flag ok
        - aggregation fail - got 10 packets, expected 1
        - after dev off, flag fail - expected on found off
        - peer flag ok
        - after gro on xdp off, gro flag ok
        - peer gro flag ok
        - tso flag ok
        - peer tso flag ok
decreasing tx channels with device down ok
        - aggregation ok
increasing tx channels with device down ok
aggregation again with default and TSO off ok

This failure is different than our known issue of this test (LP:
#1949569 with gro on/aggregation with TSO off) And we don't have this
failure on openstack cloud in the previous cycles.

I have also verified the following combinations:
* 105 kernel + 106 source code - GOOD
* 106 kernel + 106 source code - GOOD
* 111 kernel + 106 source code - BAD
* 111 kernel + 111 source code - BAD
* 106 kernel + 111 source code - GOOD

This appears to be a possible regression in the kernel to me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2065369/+subscriptions

[Bug 2067642] Re: net:tap in ubuntu_kselftests_net fails on Noble (buffer overflow detected)

[Bug 2121257] Re: [SRU] Apparmor: Unshifted uids for hardlinks and unix sockets in user namespaces

[Bug 2127764] Re: Boot up hang with ucsi call trace while plug power cord or device on tbt5 port

This bug is awaiting verification that the linux-azure-fde/6.8.0-1051.58
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-azure-fde' to 'verification-done-
noble-linux-azure-fde'. If the problem still exists, change the tag
'verification-needed-noble-linux-azure-fde' to 'verification-failed-
noble-linux-azure-fde'.

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-azure-fde-v2 verification-needed-noble-linux-azure-fde

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

Title:
Boot up hang with ucsi call trace while plug power cord or device on
tbt5 port

Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Plucky:
Won't Fix
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in linux-oem-6.17 source package in Plucky:
Invalid
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid

Bug description:
[Impact]
Boot up process may stuck with the ucsi cod trace

<4>[ 15.117180] workqueue: cannot queue ucsi_poll_worker [typec_ucsi] on wq USBC000:00-con1
<4>[ 15.117196] WARNING: CPU: 14 PID: 0 at kernel/workqueue.c:2257 __queue_work+0x2f3/0x410
<4>[ 15.117205] Modules linked in: qrtr_mhi snd_seq_dummy snd_hrtimer rfcomm snd_soc_cs42l43 spi_cs42l43 snd_soc_cs42l43_sdw pinctrl_cs42l43 snd_soc_sof_sdw snd_soc_intel_hda_dsp_common snd_soc_sdw_utils snd_sof_probes xe snd_soc_cs35l56_sdw snd_soc_cs35l56 snd_soc_wm_adsp gpu_sched snd_soc_cs35l56_shared cs42l43_sdw snd_soc_cs_amp_lib regmap_sdw drm_gpuvm cs_dsp cs42l43 drm_ttm_helper drm_exec drm_suballoc_helper snd_soc_dmic snd_sof_pci_intel_mtl snd_sof_intel_hda_generic soundwire_intel soundwire_cadence snd_sof_intel_hda_common snd_soc_hdac_hda snd_sof_intel_hda_mlink snd_sof_intel_hda snd_hda_codec_hdmi qrtr snd_sof_pci snd_sof_xtensa_dsp snd_sof intel_uncore_frequency intel_uncore_frequency_common snd_sof_utils snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi_intel_sdca_quirks soundwire_generic_allocation x86_pkg_temp_thermal snd_soc_acpi intel_powerclamp soundwire_bus cmac snd_soc_sdca coretemp algif_hash snd_soc_core algif_skcipher snd_compress ac97_bus af_alg snd_pcm_dmaengine bnep snd_hda_intel
<4>[ 15.117256] snd_intel_dspcfg dell_pc kvm_intel platform_profile snd_ctl_led snd_intel_sdw_acpi iwlmvm snd_hda_codec i915 kvm snd_hda_core mac80211 snd_hwdep snd_pcm irqbypass polyval_clmulni libarc4 snd_seq_midi polyval_generic snd_seq_midi_event ghash_clmulni_intel uvcvideo sha256_ssse3 snd_rawmidi dell_laptop sha1_ssse3 videobuf2_vmalloc aesni_intel uvc videobuf2_memops snd_seq btusb binfmt_misc videobuf2_v4l2 cmdlinepart crypto_simd drm_buddy dell_wmi videobuf2_common btrtl cryptd dell_smbios snd_seq_device spi_nor ttm btintel mtd mei_gsc_proxy intel_rapl_msr iwlwifi btbcm processor_thermal_device_pci videodev drm_display_helper snd_timer i2c_i801 btmtk processor_thermal_device dcdbas rapl nls_iso8859_1 dell_wmi_sysman intel_cstate processor_thermal_wt_hint snd cec i2c_smbus spi_intel_pci bluetooth cfg80211 mc dell_wmi_ddv dell_smm_hwmon qaic firmware_attributes_class processor_thermal_rfim dell_wmi_descriptor wmi_bmof soundcore spi_intel i2c_mux processor_thermal_rapl mei_me mhi intel_rapl_common intel_vpu
<4>[ 15.117319] rc_core mei processor_thermal_wt_req processor_thermal_power_floor i2c_algo_bit processor_thermal_mbox int3403_thermal intel_pmc_core dptf_pch_fivr int340x_thermal_zone pmt_telemetry pmt_class int3400_thermal intel_hid acpi_pad acpi_thermal_rel sparse_keymap acpi_tad intel_vsec input_leds joydev mac_hid serio_raw sch_fq_codel msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 hid_sensor_custom hid_sensor_hub intel_ishtp_hid hid_multitouch hid_generic nvme rtsx_pci_sdmmc i2c_hid_acpi ucsi_acpi video intel_lpss_pci psmouse i2c_hid typec_ucsi nvme_core intel_ish_ipc intel_lpss igc thunderbolt rtsx_pci intel_ishtp idma64 hid typec nvme_auth wmi pinctrl_meteorlake pinctrl_meteorpoint
<4>[ 15.117366] CPU: 14 UID: 0 PID: 0 Comm: swapper/14 Not tainted 6.14.0-8011-oem #11+staging.12-Ubuntu
<4>[ 15.117370] Hardware name: Dell Inc. Dell Pro Max 16 Plus MB16250/, BIOS 89.71.16 07/29/2025
<4>[ 15.117372] RIP: 0010:__queue_work+0x2f3/0x410
<4>[ 15.117376] Code: 00 00 41 83 e4 01 0f 85 49 fe ff ff 49 8b 77 18 48 8d 93 c0 00 00 00 48 c7 c7 60 22 9f 95 c6 05 06 21 66 02 01 e8 7d 19 fd ff <0f> 0b e9 24 fe ff ff 0f 0b e9 10 fe ff ff 65 8b 05 04 14 e8 6b 48
<4>[ 15.117378] RSP: 0018:ffffcc2c805d8c98 EFLAGS: 00010046
<4>[ 15.117381] RAX: 0000000000000000 RBX: ffff8aa282eac200 RCX: 0000000000000000
<4>[ 15.117383] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
<4>[ 15.117384] RBP: ffffcc2c805d8cd0 R08: 0000000000000000 R09: 0000000000000000
<4>[ 15.117386] R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
<4>[ 15.117387] R13: ffffffff941b5420 R14: ffff8aa283b33220 R15: ffff8aa283b33200
<4>[ 15.117388] FS: 0000000000000000(0000) GS:ffff8ac19ff00000(0000) knlGS:0000000000000000
<4>[ 15.117390] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
<4>[ 15.117392] CR2: 000078c0c11c5000 CR3: 000000010203f002 CR4: 0000000000f72ef0
<4>[ 15.117394] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
<4>[ 15.117395] DR3: 0000000000000000 DR6: 00000000ffff07f0 DR7: 0000000000000400
<4>[ 15.117396] PKRU: 55555554
<4>[ 15.117397] Call Trace:
<4>[ 15.117400] <IRQ>
<4>[ 15.117403] ? __pfx_delayed_work_timer_fn+0x10/0x10
<4>[ 15.117408] delayed_work_timer_fn+0x19/0x30
<4>[ 15.117411] call_timer_fn+0x2c/0x150
<4>[ 15.117414] ? __pfx_delayed_work_timer_fn+0x10/0x10
<4>[ 15.117417] __run_timers+0x1c8/0x2d0
<4>[ 15.117420] timer_expire_remote+0x52/0x80
<4>[ 15.117422] tmigr_handle_remote_cpu+0x11e/0x280
<4>[ 15.117427] tmigr_handle_remote_up+0xf1/0x140
<4>[ 15.117430] tmigr_handle_remote+0xd9/0x140
<4>[ 15.117433] run_timer_softirq+0xeb/0x100
<4>[ 15.117435] handle_softirqs+0xe4/0x340
<4>[ 15.117440] __irq_exit_rcu+0x10e/0x130
<4>[ 15.117444] irq_exit_rcu+0xe/0x20
<4>[ 15.117446] sysvec_apic_timer_interrupt+0xa0/0xc0
<4>[ 15.117450] </IRQ>
<4>[ 15.117451] <TASK>
<4>[ 15.117452] asm_sysvec_apic_timer_interrupt+0x1b/0x20

[Fix]
We submit a patch to fix this issue
https://lkml.org/lkml/2025/10/2/100
v2 - https://lkml.org/lkml/2025/10/13/312
v3 - https://lkml.org/lkml/2025/10/17/338
v4 - https://lore.kernel.org/lkml/20251218071925.3459787-1-acelan.kao@canonical.com/

[Test]
Reboot the machine with AC plug on the TBT5 port, it should always boots up correctly without call trace.

[Where problems could occur]
It should handle the destruction process correctly, and is not likely to introduce regressions.

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

[Bug 2136958] Re: Random flickering with Intel i915 (CoffeeLake and WhiskeyLake) on Linux 6.8

This bug is awaiting verification that the linux-azure-fde/6.8.0-1051.58
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-azure-fde' to 'verification-done-
noble-linux-azure-fde'. If the problem still exists, change the tag
'verification-needed-noble-linux-azure-fde' to 'verification-failed-
noble-linux-azure-fde'.

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-azure-fde-v2 verification-needed-noble-linux-azure-fde

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

Title:
Random flickering with Intel i915 (CoffeeLake and WhiskeyLake) on
Linux 6.8

Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux source package in Questing:
Fix Released
Status in linux source package in Resolute:
Fix Released

Bug description:
SRU Justification

[Impact]
Systems with Intel CoffeeLake (CFL) and WhiskeyLake (WHL) integrated graphics experience screen flickering issues when running Ubuntu kernel 6.8.0-x.

The issue occurs because:
1. Ubuntu kernel configuration enables CONFIG_INTEL_IOMMU_DEFAULT_ON and CONFIG_INTEL_IOMMU_SCALABLE_MODE_DEFAULT_ON by default (commit 77e530c1a864c)
2. These Intel integrated graphics generations have compatibility issues with DMAR (DMA Remapping) enabled
3. The interaction between IOMMU scalable mode and the i915 graphics driver causes intermittent display flickering

This is part of a broader issue affecting multiple Intel integrated
graphics generations (Skylake, KabyLake, CoffeeLake, WhiskeyLake, and
CometLake) as documented in the upstream bug report. Previous patches
have already addressed SKL, KBL, and CML; this patch completes the
series by adding CFL and WHL.

Affected hardware: Systems with Intel CoffeeLake or WhiskeyLake
integrated graphics (device IDs: 0x3E90-0x3E9C, 0x3EA0-0x3EA9)

[Fix]
Single UBUNTU SAUCE patch adds CFL and WHL device IDs to the IOMMU quirk list:

UBUNTU: SAUCE: iommu/intel: disable DMAR for CFL and WHL integrated gfx
- Adds 16 CoffeeLake device IDs (CFL_S, CFL_H, CFL_U variants)
- Adds 5 WhiskeyLake device IDs (WHL_U variants)
- Follows the same pattern as previous SKL/KBL/CML quirk patches
- Device IDs sourced from include/drm/i915_pciids.h for completeness

This is an Ubuntu-specific SAUCE patch as upstream has not yet
provided a proper fix. The quirk approach is used temporarily until a
proper upstream solution is available.

Previous related commits in this series:
- fe35c48a46619 "UBUNTU: SAUCE: iommu/intel: disable DMAR for SKL integrated gfx"
- 69a3b8e5f6ebd "UBUNTU: SAUCE: iommu/intel: disable DMAR for KBL and CML integrated gfx"

[Test Plan]
Test on hardware with CoffeeLake or WhiskeyLake integrated graphics:

1. Identify if the system has affected hardware:
```
lspci -nn | grep VGA
```
Look for Intel graphics with device IDs in the 0x3E90-0x3EA9 range.

2. Reproduce the flickering (before the fix):
a. Boot with kernel 6.8.0-x without the patch
b. Move windows around or trigger compositor effects
c. Observe intermittent screen flickering or tearing

3. Verify the fix:
a. Boot with kernel containing the patch
b. Check that IOMMU is bypassed for the graphics device:
```
sudo dmesg | grep -i "Disabling IOMMU for graphics on this chipset"
```
c. Should see: "Disabling IOMMU for graphics on this chipset"
d. Verify no flickering occurs during video playback and window animations
e. Confirm graphics performance remains normal

[Where problems could occur]
The changes affect the Intel IOMMU driver initialization for CoffeeLake and WhiskeyLake integrated graphics only.

Potential issues:

1. **Security reduction**: Disabling DMAR for integrated graphics
removes IOMMU protection for GPU DMA operations. However, integrated
graphics are generally trusted components, and the security impact is
minimal compared to the usability impact of screen flickering.

2. **Hardware-specific behavior**: Some CFL/WHL systems might not
exhibit the flickering issue, and for those systems, this patch
unnecessarily disables IOMMU for graphics. However, the functional
impact is negligible, and disabling DMAR has no negative performance
implications.

3. **Interaction with other IOMMU features**: The quirk only affects
the integrated graphics device. Other IOMMU functionality (ATS,
interrupt remapping, etc.) remains unaffected.

The impact is limited to the IOMMU configuration for CoffeeLake and
WhiskeyLake integrated graphics. All other system components continue
to benefit from IOMMU protection.

[Other Info]
This is an Ubuntu SAUCE patch (not upstream) that works around the issue until a proper upstream fix is available.

Upstream tracking bug:
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/11504

The issue was introduced in Ubuntu 6.8 kernel by commit:
77e530c1a864c "UBUNTU: [Config] enable Intel DMA remapping by default"

This patch completes a series of quirks for affected Intel graphics generations:
1. Skylake (SKL) - fe35c48a46619
2. KabyLake (KBL) and CometLake (CML) - 69a3b8e5f6ebd
3. CoffeeLake (CFL) and WhiskeyLake (WHL) - this patch

All affected device IDs were verified against the upstream i915
driver's device ID definitions in include/drm/i915_pciids.h.

======================================

Random flickering of the screen when cursor is in the lower part of
the screen. The flickering stops when mouse is again moved.

This problem happens on my two laptops (CoffeeLake and WhiskeyLake), details below. Adding
intel_iommu=igfx_off to kernel command line solves this problem.
Bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2062951/+index?comments=all solves the problem for some architectures, but it is now closed. Hence I opened new bug report.

Laptop 1:

$ lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b]
DeviceName: Onboard IGD
Subsystem: Hewlett-Packard Company CoffeeLake-H GT2 [UHD Graphics 630] [103c:8427]
Kernel driver in use: i915
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] (rev a1)
Subsystem: Hewlett-Packard Company GP107GLM [Quadro P1000 Mobile] [103c:8427]
Kernel driver in use: nvidia
Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia

# System Details Report
---

## Report details
- **Date generated:** 2025-11-24 21:29:40

## Hardware Information:
- **Hardware Model:** HP HP ZBook Studio G5
- **Memory:** 16.0 GiB
- **Processor:** Intel® Core™ i7-8750H × 12
- **Graphics:** Intel® UHD Graphics 630 (CFL GT2)
- **Graphics 1:** Quadro P1000
- **Disk Capacity:** 512.1 GB

## Software Information:
- **Firmware Version:** Q71 Ver. 01.32.00
- **OS Name:** Ubuntu 24.04.3 LTS
- **OS Build:** (null)
- **OS Type:** 64-bit
- **GNOME Version:** 46
- **Windowing System:** X11
- **Kernel Version:** Linux 6.8.0-88-generic

Laptop 2:

$ lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02)
Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:2281]
Kernel driver in use: i915
Kernel modules: i915

# System Details Report
---

## Report details
- **Date generated:** 2025-11-26 14:28:35

## Hardware Information:
- **Hardware Model:** Lenovo ThinkPad P53s
- **Memory:** 40.0 GiB
- **Processor:** Intel® Core™ i7-8565U × 8
- **Graphics:** Intel® UHD Graphics 620 (WHL GT2)
- **Graphics 1:** NV138
- **Disk Capacity:** 1.0 TB

## Software Information:
- **Firmware Version:** N2IETA6W (1.84 )
- **OS Name:** Ubuntu 24.04.3 LTS
- **OS Build:** (null)
- **OS Type:** 64-bit
- **GNOME Version:** 46
- **Windowing System:** X11
- **Kernel Version:** Linux 6.8.0-88-generic

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

[Bug 2137613] Re: TBT call trace while connecting TBT4 monitor on TBT5 port

[Bug 2138120] Re: x86: tsc: Fix TSC clock source being disabled when SNC is enabled causing fall back to less precise HPET

[Bug 2141314] Re: xhci_find_slot_id_by_port kernel panic on boot on arm64

This bug is awaiting verification that the linux-azure-fde/6.8.0-1051.58
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-azure-fde' to 'verification-done-
noble-linux-azure-fde'. If the problem still exists, change the tag
'verification-needed-noble-linux-azure-fde' to 'verification-failed-
noble-linux-azure-fde'.

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-azure-fde-v2 verification-needed-noble-linux-azure-fde

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

Title:
xhci_find_slot_id_by_port kernel panic on boot on arm64

Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
Fix Released

Bug description:
On noble:linux 6.8.0-102.102 running on openstack arm64-vm the kernel panics and doesn't boot properly.
The commit inducing the regression is

xhci: fix stale flag preventig URBs after link state error is cleared

[ 3.942479] xhci_hcd 0000:04:00.0: xHCI Host Controller
[ 3.945493] xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 1
[ 3.945585] virtio_net virtio0 enp3s0: renamed from eth0
[ 3.947045] xhci_hcd 0000:04:00.0: hcc params 0x00087001 hci version 0x100 quirks 0x0000000000000010
[ 3.954946] xhci_hcd 0000:04:00.0: xHCI Host Controller
[ 3.955625] xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus number 2
[ 3.958265] xhci_hcd 0000:04:00.0: Host supports USB 3.0 SuperSpeed
[ 3.958951] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
[ 3.959702] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.960384] usb usb1: Product: xHCI Host Controller
[ 3.960823] usb usb1: Manufacturer: Linux 6.8.0-102-generic xhci-hcd
[ 3.961348] usb usb1: SerialNumber: 0000:04:00.0
[ 3.962227] hub 1-0:1.0: USB hub found
[ 3.962897] hub 1-0:1.0: 4 ports detected
[ 3.963674] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[ 3.964770] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.08
[ 3.966255] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.966994] usb usb2: Product: xHCI Host Controller
[ 3.967431] usb usb2: Manufacturer: Linux 6.8.0-102-generic xhci-hcd
[ 3.967988] usb usb2: SerialNumber: 0000:04:00.0
[ 3.969233] hub 2-0:1.0: USB hub found
[ 3.969858] hub 2-0:1.0: 4 ports detected
[ 4.009945] [drm] pci: virtio-gpu-pci detected at 0000:09:00.0
[ 4.010569] [drm] features: -virgl +edid -resource_blob -host_visible
[ 4.010571] [drm] features: -context_init
[ 4.018692] [drm] number of scanouts: 1
[ 4.019325] [drm] number of cap sets: 0
[ 4.020235] [drm] Initialized virtio_gpu 0.1.0 0 for 0000:09:00.0 on minor 0
[ 4.024718] Console: switching to colour frame buffer device 160x50
[ 4.033596] virtio-pci 0000:09:00.0: [drm] fb0: virtio_gpudrmfb frame buffer device
Begin: Loading essential drivers ... [ 4.091843] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000a0
[ 4.092765] Mem abort info:
[ 4.093051] ESR = 0x0000000096000004
[ 4.093401] EC = 0x25: DABT (current EL), IL = 32 bits
[ 4.093948] SET = 0, FnV = 0
[ 4.094235] EA = 0, S1PTW = 0
[ 4.094531] FSC = 0x04: level 0 translation fault
[ 4.094994] Data abort info:
[ 4.095264] ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
[ 4.095834] CM = 0, WnR = 0, TnD = 0, TagAccess = 0
[ 4.096349] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
[ 4.096862] user pgtable: 4k pages, 48-bit VAs, pgdp=000000010864e000
[ 4.097456] [00000000000000a0] pgd=0000000000000000, p4d=0000000000000000
[ 4.098115] Internal error: Oops: 0000000096000004 [#1] SMP
[ 4.098629] Modules linked in: crct10dif_ce polyval_ce polyval_generic virtio_gpu ghash_ce virtio_dma_buf sm4 sha2_ce sha256_arm64 sha1_ce virtio_rng xhci_pci xhci_pci_renesas aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher
[ 4.100591] CPU: 0 PID: 185 Comm: init Not tainted 6.8.0-102-generic #102-Ubuntu
[ 4.101297] Hardware name: QEMU KVM Virtual Machine, BIOS 2025.02-8~22.04.0~ppa3 05/14/2025
[ 4.102096] pstate: 804000c5 (Nzcv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 4.102738] pc : xhci_find_slot_id_by_port+0x80/0x150
[ 4.103224] lr : handle_port_status.isra.0+0xa8/0x9c0
[ 4.103692] sp : ffff800080003d80
[ 4.104020] x29: ffff800080003d80 x28: ffff0000c7d88000 x27: 0000000000000001
[ 4.104683] x26: 0000000000000001 x25: 0000000000000000 x24: ffff0000c7b6d3c0
[ 4.105743] x23: 0000000000000001 x22: ffff0000c4116800 x21: 0000000000000001
[ 4.106832] x20: ffff0000c86ec000 x19: 0000000000000001 x18: ffff800080005060
[ 4.107892] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000
[ 4.108945] x14: 0000000000000000 x13: 0000000000000000 x12: 0000000000000000
[ 4.109983] x11: ffff0000c6ea7908 x10: 0000000000000000 x9 : ffffcafdb9b9e4a0
[ 4.111016] x8 : ffff8000806d3d18 x7 : 0000000000000000 x6 : 0000000000000000
[ 4.112044] x5 : 0000000000000000 x4 : 0000000000000000 x3 : 0000000000008801
[ 4.113071] x2 : 0000000000000001 x1 : 0000000000000001 x0 : 0000000000000000
[ 4.114095] Call trace:
[ 4.114666] xhci_find_slot_id_by_port+0x80/0x150
[ 4.115454] handle_port_status.isra.0+0xa8/0x9c0
[ 4.116276] xhci_handle_event+0x1d8/0x2b8
[ 4.117045] xhci_irq+0xe8/0x588
[ 4.117693] xhci_msi_irq+0x20/0x48
[ 4.118358] __handle_irq_event_percpu+0x68/0x2c0
[ 4.119149] handle_irq_event+0x58/0xe8
[ 4.119904] handle_fasteoi_irq+0xb0/0x218
[ 4.120633] handle_irq_desc+0x58/0x98
[ 4.121459] generic_handle_domain_irq+0x28/0x50
[ 4.122278] __gic_handle_irq_from_irqson.isra.0+0x180/0x310
[ 4.123155] gic_handle_irq+0x2c/0xa0
[ 4.123831] call_on_irq_stack+0x48/0x68
[ 4.124523] do_interrupt_handler+0xb0/0xc0
[ 4.125308] el1_interrupt+0x48/0xf0
[ 4.125999] el1h_64_irq_handler+0x1c/0x40
[ 4.126694] el1h_64_irq+0x7c/0x80
[ 4.127346] percpu_counter_add_batch+0x7c/0x170
[ 4.128118] set_pte_range+0x100/0x2c8
[ 4.128846] filemap_map_pages+0x198/0x5e8
[ 4.129534] do_read_fault+0x150/0x2f0
[ 4.130196] do_pte_missing+0x208/0x3f8
[ 4.130874] handle_pte_fault+0x12c/0x1a0
[ 4.131549] __handle_mm_fault+0x24c/0x400
[ 4.132250] handle_mm_fault+0xac/0x2e0
[ 4.132919] do_page_fault+0x104/0x538
[ 4.133568] do_translation_fault+0x7c/0xd8
[ 4.134312] do_mem_abort+0x50/0xd0
[ 4.134952] el0_da+0x4c/0x178
[ 4.135526] el0t_64_sync_handler+0xdc/0x158
[ 4.136236] el0t_64_sync+0x1b0/0x1b8
[ 4.136911] Code: b4fffe76 f10402bf 54000542 b9401ec4 (b940a323)
[ 4.137740] ---[ end trace 0000000000000000 ]---
[ 4.138432] Kernel panic - not syncing: Oops: Fatal exception in interrupt
[ 4.139334] SMP: stopping secondary CPUs
[ 4.140021] Kernel Offset: 0x4afd38a10000 from 0xffff800080000000
[ 4.140857] PHYS_OFFSET: 0x40000000
[ 4.141438] CPU features: 0x1,00000021,7002014a,2141720b
[ 4.142251] Memory Limit: none
[ 4.142788] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]---

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

[Bug 2141778] Re: Change of ABI in 6.8.0 kernel breaks some OTT modules

[Bug 2143197] Re: UBUNTU: SAUCE: igc: Increase Thunderbolt MAC passthrough delay to 1000ms

** Tags removed: verification-needed-noble-linux-oem-6.17
** Tags added: verification-done-noble-linux-oem-6.17

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

Title:
UBUNTU: SAUCE: igc: Increase Thunderbolt MAC passthrough delay to
1000ms

Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid

Bug description:
BugLink: https://bugs.launchpad.net/bugs/2143197

[Impact]
Dell Thunderbolt dock ethernet (Intel I226 NIC) can fail to initialize after
hotplug with MAC passthrough enabled. After unplug/replug, the interface may appear with an dock MAC address but not MAC passthrough address then cause stale MAC and wired networking does not work.
Cold boot is unaffected; issue is hotplug-specific.

Affected systems include Dell platforms with Thunderbolt docks such as
SD25TB5-class docks carrying Intel I226 ethernet.

[Fix]
Increase the existing Thunderbolt MAC passthrough wait in igc probe path:
- from 600ms
- to 1000ms

Ubuntu already carries a SAUCE workaround (commit 534981aaa831) that uses
fixed delay timing. Newer Dell docks need a longer timing window.

Debug testing shows BIOS MAC update timing:
- cold boot: MAC already correct at probe start
- hotplug: MAC becomes correct at ~300-800ms after probe starts

Use 1000ms (observed 800ms worst-case + margin) to make hotplug
reliable.

Upstream context:
https://lore.kernel.org/lkml/20210702045120.22855-2-aaron.ma@canonical.com/
(Upstream preferred polling over fixed delay; Ubuntu keeps minimal stable
fixed-delay workaround.)

[Test Plan]
1. Boot with dock attached; confirm interface has valid MAC and link works.
2. Unplug dock, wait 5s, replug, wait for enumeration.
3. Verify MAC is valid/correct and connectivity works.
4. Repeat hotplug cycle 10 times.

Expected results:
- Without this change: intermittent hotplug failures (~50-80% observed).
- With this change: MAC is correct and networking works on every cycle.

[Where problems could occur]
- Probe time for Thunderbolt-attached igc devices increases by 400ms.
- Scope is limited to pci_is_thunderbolt_attached() path.
- If a future dock requires >1000ms, hotplug failure could still occur.
- No functional changes beyond extending an existing sleep.

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

[Bug 2144336] Re: Support Nova Lake P

** Changed in: linux (Ubuntu Resolute)
Status: In Progress => Incomplete

** Changed in: linux (Ubuntu Resolute)
Importance: Undecided => Wishlist

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

Title:
Support Nova Lake P

Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Resolute:
Incomplete

Bug description:
Nova-lake P support is missing in 7.0 but has been merged in linux-next and expected in 7.1
Patches enabling Xe3p_LPG are required, which were submitted in beginning of February and merged upstream [0].

There is two additionnal commits on top of the upstream submission:
- A non upstream patchset to enable the probing of such hardware by default.
- A fixup commit submitted the 3rd March changing the GuC firmware expected [1]

This patchset is submitted in collaboration with intel.

0: https://lore.kernel.org/all/20260206-nvl-p-upstreaming-v3-0-636e1ad32688@intel.com/
1: https://patchwork.freedesktop.org/series/162530/#rev2

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

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

Moved iwlwifi-gl-c0-fm-c0-c102.ucode and iwlwifi-gl-c0-fm-c0-c101.ucode
to bug 2146301, leaving ibt-00a0-00a1-* for WhP2/SpP2 BT (IOSF) as the
last missing jigsaw.

--
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 2144926] Re: Network issues without any kind of visible dropped packages

** Package changed: ubuntu => linux (Ubuntu)

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

Title:
Network issues without any kind of visible dropped packages

Status in linux package in Ubuntu:
New

Bug description:
Hi there,

we upgraded some of our 22.04er VMs this week and encounter some weird
network issues.

We couldn't find any dropped packages or other "visible" signs.

After a while of try and error with ping, mtr and traceroute we
realized curl was behaving "weirdly"

After a reboot we were able to run e.g. `curl -I www.google.com`
exactly once successfully and after that curl "hang" for a while, then
it worked for a short while and hang again.

To ping a destination always worked and was not flaky at all, so we
assume it could be something with http?

We found this:
https://www.ubuntuupdates.org/package/core/jammy/main/updates/linux-tools-5.15.0-173-generic

We read that "apparmor: fix memory leak in verify_header" so on a
hunch we downgraded to linux-image-5.15.0-171-generic from linux-
image-5.15.0-173-generic and all network issues disappeared.

I hope this is any helpful

p.s I wasn't able to chose the package name so I chose "I don't know", but it has to do with linux-image-5.15.0-173-generic

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-173-generic 5.15.0-173.183
ProcVersionSignature: Ubuntu 5.15.0-173.183-generic 5.15.198
Uname: Linux 5.15.0-173-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Mar 16 06:32 seq
crw-rw---- 1 root audio 116, 33 Mar 16 06:32 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82.10
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
CloudArchitecture: x86_64
CloudID: hetzner
CloudName: hetzner
CloudPlatform: hetzner
CloudSubPlatform: unknown
Date: Thu Mar 19 08:50:01 2026
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
MachineType: Hetzner vServer
PciMultimedia:

ProcFB: 0 virtio_gpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-173-generic root=UUID=be1e37b2-1f27-4d9f-8cc5-c947b721042d ro consoleblank=0 systemd.show_status=true console=tty1 console=ttyS0
RelatedPackageVersions:
linux-restricted-modules-5.15.0-173-generic N/A
linux-backports-modules-5.15.0-173-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.41
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2017
dmi.bios.release: 1.0
dmi.bios.vendor: Hetzner
dmi.bios.version: 20171111
dmi.board.name: Standard PC (Q35 + ICH9, 2009)
dmi.board.vendor: KVM
dmi.board.version: pc-q35-6.2
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: NotSpecified
dmi.modalias: dmi:bvnHetzner:bvr20171111:bd11/11/2017:br1.0:svnHetzner:pnvServer:pvr20171111:rvnKVM:rnStandardPC(Q35+ICH9,2009):rvrpc-q35-6.2:cvnQEMU:ct1:cvrNotSpecified:skuTM:
dmi.product.family: Hetzner_vServer
dmi.product.name: vServer
dmi.product.sku: TM
dmi.product.version: 20171111
dmi.sys.vendor: Hetzner

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