Ubuntu
linux package

i40e driver is triggering VF resets on every link state change

Bug #2130552 reported by Robert Malz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Status tracked in Resolute
Jammy
Fix Released
Medium
Unassigned
Noble
Fix Released
Medium
Unassigned
Plucky
Fix Released
Medium
Unassigned
Questing
Fix Released
Medium
Unassigned
Resolute
Fix Released
Medium
Unassigned

Bug Description

[ Impact ]

 * In the i40e driver, every VF link state change request is causing a VF reset,
   even if the requested change is already set. This leads to unnecessary VF
   resets and can cause performance degradation or instability in the VF
   driver, particularly in DPDK environments.

 * With the proposed patch, i40e will skip VF link state change requests when the
   desired link state matches the current configuration. This prevents
   unnecessary VF resets and reduces PF-VF communication overhead.

 * The issue was originally detected by analyzing DPDK VF driver issues during
   OpenStack Neutron restarts. In such cases, i40e will issue an unnecessary VF
   reset request which causes instability in the DPDK driver.

[ Test Plan ]

 * The issue can be reproduced by triggering VF link state changes multiple times
   with the same requested link state.

 * To reproduce the problem, run the following command multiple times
   on the same interface: 'ip link set <ifname> vf 0 state auto'.
   Every time the command is executed, the PF driver will trigger a VF reset.

 * Monitor for VF reset events using dmesg or appropriate logging mechanisms
   to confirm the issue and verify the fix.

 * Regression testing should include:
   - Verify normal VF link state changes still work correctly when state actually changes
   - Validate that legitimate state changes still trigger resets when needed

[ Where problems could occur ]

 * Changes only affect the i40e .ndo_set_vf_link_state routine. In case
   of any regressions, only the ability to set VF link state changes could be
   impacted.

 * The patch was verified locally and passed Intel internal test execution.

 * Potential failure modes:
   - Logic error in state comparison could prevent legitimate state changes
   - Incorrect state tracking could lead to inconsistent VF behavior

 * Risk mitigation:
   - The change is isolated to a specific code path in the i40e driver
   - Existing VF functionality remains unchanged when state changes are needed
   - The patch adds a simple comparison check before existing link change routine

[ Other Info ]

 * At the time of writing this document, the target patch is still in the net-next
   tree and has not yet been merged into mainline.

 * Patch: a7ae783da0b919550e260aebfca1c6ef030b99a4 from netdev/net-next

 * Patch applies on most versions without any conflicts

 * No dependencies on other patches

 * Mainline status: Patch is currently in net-next tree, awaiting mainline merge

 * Backport requirements: Patch should apply cleanly to Ubuntu kernel versions

 * VF reset during link state change was added as a part of 31deb12e85c35ddd2c037f0107d05d8674cab2c0 (upstream) commit, which is included in the Kernels starting from 5.15

Ubuntu Kernel Bot (ubuntu-kernel-bot)
tags: added: kernel-daily-bug
Stefan Bader (smb)
Changed in linux (Ubuntu Resolute):
importance: Undecided → Medium
Changed in linux (Ubuntu Questing):
importance: Undecided → Medium
Changed in linux (Ubuntu Plucky):
importance: Undecided → Medium
Changed in linux (Ubuntu Noble):
importance: Undecided → Medium
Changed in linux (Ubuntu Jammy):
importance: Undecided → Medium
Changed in linux (Ubuntu Resolute):
status: New → Triaged
Changed in linux (Ubuntu Questing):
status: New → Fix Committed
Changed in linux (Ubuntu Plucky):
status: New → Fix Committed
Changed in linux (Ubuntu Noble):
status: New → Fix Committed
Changed in linux (Ubuntu Jammy):
status: New → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/6.8.0-89.90 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
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/6.14.0-37.37 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-plucky-linux' to 'verification-done-plucky-linux'. If the problem still exists, change the tag 'verification-needed-plucky-linux' to 'verification-failed-plucky-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-plucky-linux-v2 verification-needed-plucky-linux
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.15.0-164.174 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' to 'verification-done-jammy-linux'. If the problem still exists, change the tag 'verification-needed-jammy-linux' to 'verification-failed-jammy-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-jammy-linux-v2 verification-needed-jammy-linux
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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-fde-6.8-v2 verification-needed-jammy-linux-azure-fde-6.8
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/6.17.0-8.8 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-questing-linux' to 'verification-done-questing-linux'. If the problem still exists, change the tag 'verification-needed-questing-linux' to 'verification-failed-questing-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-questing-linux-v2 verification-needed-questing-linux
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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

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

tags: added: kernel-spammed-noble-linux-aws-6.17-v2 verification-needed-noble-linux-aws-6.17
Revision history for this message
Manuel Diewald (diewald) wrote :
Download full text (10.6 KiB)

Verification for jammy:linux on machine beldam:

+ uname -a
Linux beldam 5.15.0-163-generic #173-Ubuntu SMP Tue Oct 14 17:51:00 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
+ echo 0
+ echo
+ echo
+ echo 0
+ echo
+ echo function
+ echo i40e_vc_reset_vf
+ echo 'p:i40e_probe i40e_ndo_set_vf_link_state netdev=%di vf_id=%si:x32 link=%dx:x32'
+ echo 1
+ echo 1
+ echo 4
+ sudo tee /sys/class/net/enp176s0f0/device/sriov_numvfs
4
+ sleep 5
+ ip link set enp176s0f0 vf 0 state auto
+ sleep 5
+ ip link set enp176s0f0 vf 0 state auto
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether 5a:ad:a2:b2:a4:90 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 1 link/ether 6a:f9:15:ff:2e:da brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether 06:fd:29:99:12:ee brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether 3e:37:a7:f9:6b:e2 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
+ ip link set enp176s0f0 vf 0 state enable
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether 5a:ad:a2:b2:a4:90 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state enable, trust off
    vf 1 link/ether 6a:f9:15:ff:2e:da brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether 06:fd:29:99:12:ee brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether 3e:37:a7:f9:6b:e2 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
+ ip link set enp176s0f0 vf 0 state disable
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether 5a:ad:a2:b2:a4:90 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state disable, trust off
    vf 1 link/ether 6a:f9:15:ff:2e:da brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether 06:fd:29:99:12:ee brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether 3e:37:a7:f9:6b:e2 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
+ ip link set enp176s0f0 vf 0 state auto
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether 5a:ad:a2:b2:a4:90 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 1 link/ether 6a:f9:15:ff:2e:da brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether 06:fd:29:99:12:ee brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether 3e:37:a7:f9:6b:e2 brd ff...

tags: added: verification-done-jammy-linux
removed: verification-needed-jammy-linux
Revision history for this message
Manuel Diewald (diewald) wrote :
Download full text (10.6 KiB)

Verification for noble:linux on machine beldam:

+ uname -a
Linux beldam 6.8.0-88-generic #89-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct 11 01:02:46 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
+ echo 0
+ echo
+ echo
+ echo 0
+ echo
+ echo function
+ echo i40e_vc_reset_vf
+ echo 'p:i40e_probe i40e_ndo_set_vf_link_state netdev=%di vf_id=%si:x32 link=%dx:x32'
+ echo 1
+ echo 1
+ echo 4
+ sudo tee /sys/class/net/enp176s0f0/device/sriov_numvfs
4
+ sleep 5
+ ip link set enp176s0f0 vf 0 state auto
+ sleep 5
+ ip link set enp176s0f0 vf 0 state auto
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether 4a:e6:dc:cb:e6:eb brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 1 link/ether f2:98:54:ab:51:55 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether 16:a4:b0:c1:76:5c brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether b6:92:49:f8:46:3d brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
+ ip link set enp176s0f0 vf 0 state enable
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether 4a:e6:dc:cb:e6:eb brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state enable, trust off
    vf 1 link/ether f2:98:54:ab:51:55 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether 16:a4:b0:c1:76:5c brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether b6:92:49:f8:46:3d brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
+ ip link set enp176s0f0 vf 0 state disable
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether 4a:e6:dc:cb:e6:eb brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state disable, trust off
    vf 1 link/ether f2:98:54:ab:51:55 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether 16:a4:b0:c1:76:5c brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether b6:92:49:f8:46:3d brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
+ ip link set enp176s0f0 vf 0 state auto
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether 4a:e6:dc:cb:e6:eb brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 1 link/ether f2:98:54:ab:51:55 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether 16:a4:b0:c1:76:5c brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether b6:92:49:f8...

tags: added: verification-done-noble-linux
removed: verification-needed-noble-linux
Revision history for this message
Manuel Diewald (diewald) wrote :

For reference, I'm using this script to perform verification:

set -xe
uname -a
echo 0 > /sys/kernel/debug/tracing/tracing_on
echo > /sys/kernel/debug/tracing/set_event
echo > /sys/kernel/debug/tracing/set_ftrace_filter
echo 0 > /sys/kernel/debug/tracing/options/function-trace
echo > /sys/kernel/debug/tracing/trace
echo function > /sys/kernel/debug/tracing/current_tracer
echo i40e_vc_reset_vf >> /sys/kernel/debug/tracing/set_ftrace_filter
echo 'p:i40e_probe i40e_ndo_set_vf_link_state netdev=%di vf_id=%si:x32 link=%dx:x32' > /sys/kernel/debug/tracing/kprobe_events
echo 1 > /sys/kernel/debug/tracing/events/kprobes/i40e_probe/enable
echo 1 > /sys/kernel/debug/tracing/tracing_on
# reproduce the problem or restart neutron_sriov_agent and wait couple of seconds
echo 4 | sudo tee /sys/class/net/enp176s0f0/device/sriov_numvfs
sleep 5
ip link set enp176s0f0 vf 0 state auto
sleep 5
ip link set enp176s0f0 vf 0 state auto
sleep 5
ip link show enp176s0f0
ip link set enp176s0f0 vf 0 state enable
sleep 5
ip link show enp176s0f0
ip link set enp176s0f0 vf 0 state disable
sleep 5
ip link show enp176s0f0
ip link set enp176s0f0 vf 0 state auto
sleep 5
ip link show enp176s0f0
ip link set enp176s0f0 vf 0 state auto
sleep 5
ip link set enp176s0f0 vf 0 state auto
sleep 5
echo 0 > /sys/kernel/debug/tracing/tracing_on
cp /sys/kernel/debug/tracing/trace /tmp/trace.out
# share /tmp/trace.out
cat /tmp/trace.out

Revision history for this message
Manuel Diewald (diewald) wrote :
Download full text (11.1 KiB)

Verification for plucky:linux on machine beldam:

+ uname -a
Linux beldam 6.14.0-36-generic #36-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct 11 02:18:29 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
+ echo 0
+ echo
+ echo
+ echo 0
+ echo
+ echo function
+ echo i40e_vc_reset_vf
+ echo 'p:i40e_probe i40e_ndo_set_vf_link_state netdev=%di vf_id=%si:x32 link=%dx:x32'
+ echo 1
+ echo 1
+ echo 4
+ sudo tee /sys/class/net/enp176s0f0/device/sriov_numvfs
4
+ sleep 5
+ ip link set enp176s0f0 vf 0 state auto
+ sleep 5
+ ip link set enp176s0f0 vf 0 state auto
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether 76:42:9d:8b:8d:d3 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 1 link/ether ce:ae:3c:f3:e8:e6 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether fa:46:83:92:76:eb brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether c6:e0:00:68:14:f3 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    altname enp176s0f0np0
    altname enx40a6b75d3988
+ ip link set enp176s0f0 vf 0 state enable
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether 76:42:9d:8b:8d:d3 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state enable, trust off
    vf 1 link/ether ce:ae:3c:f3:e8:e6 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether fa:46:83:92:76:eb brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether c6:e0:00:68:14:f3 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    altname enp176s0f0np0
    altname enx40a6b75d3988
+ ip link set enp176s0f0 vf 0 state disable
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether 76:42:9d:8b:8d:d3 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state disable, trust off
    vf 1 link/ether ce:ae:3c:f3:e8:e6 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether fa:46:83:92:76:eb brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether c6:e0:00:68:14:f3 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    altname enp176s0f0np0
    altname enx40a6b75d3988
+ ip link set enp176s0f0 vf 0 state auto
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether 76:42:9d:8b:8d:d3 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 1 link/ether ce:ae:3c:f3:e8:e6 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-stat...

tags: added: verification-done-plucky-linux
removed: verification-needed-plucky-linux
Revision history for this message
Manuel Diewald (diewald) wrote :
Download full text (11.0 KiB)

Verification for questing:linux on machine beldam:

+ uname -a
Linux beldam 6.17.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct 18 10:10:29 UTC 2025 x86_64 GNU/Linux
+ echo 0
+ echo
+ echo
+ echo 0
+ echo
+ echo function
+ echo i40e_vc_reset_vf
+ echo 'p:i40e_probe i40e_ndo_set_vf_link_state netdev=%di vf_id=%si:x32 link=%dx:x32'
+ echo 1
+ echo 1
+ echo 4
+ sudo tee /sys/class/net/enp176s0f0/device/sriov_numvfs
4
+ sleep 5
+ ip link set enp176s0f0 vf 0 state auto
+ sleep 5
+ ip link set enp176s0f0 vf 0 state auto
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether aa:31:60:41:6f:a1 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 1 link/ether 02:25:ef:ec:ca:6e brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether 7e:dd:7a:09:15:ba brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether 1e:1c:65:fd:d5:48 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    altname enp176s0f0np0
    altname enx40a6b75d3988
+ ip link set enp176s0f0 vf 0 state enable
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether aa:31:60:41:6f:a1 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state enable, trust off
    vf 1 link/ether 02:25:ef:ec:ca:6e brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether 7e:dd:7a:09:15:ba brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether 1e:1c:65:fd:d5:48 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    altname enp176s0f0np0
    altname enx40a6b75d3988
+ ip link set enp176s0f0 vf 0 state disable
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether aa:31:60:41:6f:a1 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state disable, trust off
    vf 1 link/ether 02:25:ef:ec:ca:6e brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 2 link/ether 7e:dd:7a:09:15:ba brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 3 link/ether 1e:1c:65:fd:d5:48 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    altname enp176s0f0np0
    altname enx40a6b75d3988
+ ip link set enp176s0f0 vf 0 state auto
+ sleep 5
+ ip link show enp176s0f0
2: enp176s0f0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 40:a6:b7:5d:39:88 brd ff:ff:ff:ff:ff:ff
    vf 0 link/ether aa:31:60:41:6f:a1 brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust off
    vf 1 link/ether 02:25:ef:ec:ca:6e brd ff:ff:ff:ff:ff:ff, spoof checking on, link-state auto, trust ...

tags: added: verification-done-questing-linux
removed: verification-needed-questing-linux
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 6.17.0-8.8

---------------
linux (6.17.0-8.8) questing; urgency=medium

  * questing/linux: 6.17.0-8.8 -proposed tracker (LP: #2131554)

  * crash when reading from /sys/kernel/tracing/rv/enabled_monitors
    (LP: #2131136)
    - rv: Fully convert enabled_monitors to use list_head as iterator

  * i40e driver is triggering VF resets on every link state change
    (LP: #2130552)
    - i40e: avoid redundant VF link state updates

  * kernel crash on bootup for some arm64 machines (LP: #2129770)
    - KVM: arm64: Guard PMSCR_EL1 initialization with SPE presence check

  * CVE-2025-40018
    - ipvs: Defer ip_vs_ftp unregister during netns cleanup

 -- Manuel Diewald <email address hidden> Fri, 14 Nov 2025 17:53:03 +0100

Changed in linux (Ubuntu Questing):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 6.14.0-37.37

---------------
linux (6.14.0-37.37) plucky; urgency=medium

  * plucky/linux: 6.14.0-37.37 -proposed tracker (LP: #2131513)

  * Poweroff not working consistently after upgrading kernel 6.14.0-17.17 or
    later (LP: #2115860)
    - drm/amd: Unify shutdown() callback behavior
    - drm/amd: Stop exporting amdgpu_device_ip_suspend() outside amdgpu_device
    - drm/amd: Remove comment about handling errors in
      amdgpu_device_ip_suspend_phase1()
    - drm/amd: Don't always set IP block HW status to false
    - drm/amd: Pass IP suspend errors up to callers
    - drm/amd: Avoid evicting resources at S5

  * CAP_PERFMON insufficient to get perf data (LP: #2131046)
    - SAUCE: perf/core: Allow CAP_PERFMON for paranoid level 4

  * i40e driver is triggering VF resets on every link state change
    (LP: #2130552)
    - i40e: avoid redundant VF link state updates

  * kernel: sysfs: cannot create duplicate filename
    '/bus/platform/devices/iTCO_wdt' (LP: #2121997)
    - i2c: i801: Hide Intel Birch Stream SoC TCO WDT

  * Fix incorrect bug number for CONFIG_KERNEL_ZSTD (LP: #2127676)
    - [Config] Fix bug note for CONFIG_KERNEL_ZSTD

  * CVE-2025-39993
    - media: rc: fix races with imon_disconnect()

  * CVE-2025-40018
    - ipvs: Defer ip_vs_ftp unregister during netns cleanup

  * CVE-2025-39964
    - crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg
    - crypto: af_alg - Fix incorrect boolean values in af_alg_ctx

  * CVE-2025-39946
    - tls: make sure to abort the stream if headers are bogus

 -- Manuel Diewald <email address hidden> Fri, 14 Nov 2025 17:52:55 +0100

Changed in linux (Ubuntu Plucky):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 5.15.0-164.174

---------------
linux (5.15.0-164.174) jammy; urgency=medium

  * jammy/linux: 5.15.0-164.174 -proposed tracker (LP: #2131429)

  * CVE-2024-53218
    - f2fs: fix race in concurrent f2fs_stop_gc_thread

  * CVE-2024-47691
    - f2fs: fix to avoid use-after-free in f2fs_stop_gc_thread()

  * CVE-2025-39993
    - media: rc: fix races with imon_disconnect()

  * i40e driver is triggering VF resets on every link state change
    (LP: #2130552)
    - i40e: avoid redundant VF link state updates

  * CVE-2025-40018
    - ipvs: Defer ip_vs_ftp unregister during netns cleanup

  * CVE-2025-21855
    - ibmvnic: Don't reference skb after sending to VIOS

  * CVE-2024-50067
    - uprobes: encapsulate preparation of uprobe args buffer
    - uprobe: avoid out-of-bounds memory access of fetching args

  * CVE-2024-53090
    - afs: Fix lock recursion

  * CVE-2025-39964
    - crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg
    - crypto: af_alg - Fix incorrect boolean values in af_alg_ctx

  * CVE-2022-49390
    - macsec: fix UAF bug for real_dev

 -- Manuel Diewald <email address hidden> Fri, 14 Nov 2025 17:49:39 +0100

Changed in linux (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 6.8.0-90.91

---------------
linux (6.8.0-90.91) noble; urgency=medium

  * noble/linux: 6.8.0-90.91 -proposed tracker (LP: #2131785)

  * cifs: Fix memory leak of a folio every call to cifs_writepages_begin()
    (LP: #2131213)
    - cifs: fix pagecache leak when do writepages

linux (6.8.0-89.90) noble; urgency=medium

  * noble/linux: 6.8.0-89.90 -proposed tracker (LP: #2131481)

  * CVE-2025-39993
    - media: rc: fix races with imon_disconnect()

  * Audio output fails on internal speakers when using kernel 6.8.0-84 and
    newer. (LP: #2130212)
    - Revert "ASoC: cs35l56: Prevent races when soft-resetting using SPI
      control"

  * i40e driver is triggering VF resets on every link state change
    (LP: #2130552)
    - i40e: avoid redundant VF link state updates

  * CVE-2025-40018
    - ipvs: Defer ip_vs_ftp unregister during netns cleanup

  * CVE-2025-39964
    - crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg
    - crypto: af_alg - Fix incorrect boolean values in af_alg_ctx

  * CVE-2025-37958
    - mm/huge_memory: fix dereferencing invalid pmd migration entry

  * CVE-2025-38666
    - net: appletalk: Fix use-after-free in AARP proxy probe

 -- Manuel Diewald <email address hidden> Tue, 18 Nov 2025 12:26:33 +0100

Changed in linux (Ubuntu Noble):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-realtime-6.17/6.17.0-1004.5~24.04.2 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-realtime-6.17' to 'verification-done-noble-linux-realtime-6.17'. If the problem still exists, change the tag 'verification-needed-noble-linux-realtime-6.17' to 'verification-failed-noble-linux-realtime-6.17'.

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-realtime-6.17-v2 verification-needed-noble-linux-realtime-6.17
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 6.17.0-8.8

---------------
linux (6.17.0-8.8) questing; urgency=medium

  * questing/linux: 6.17.0-8.8 -proposed tracker (LP: #2131554)

  * crash when reading from /sys/kernel/tracing/rv/enabled_monitors
    (LP: #2131136)
    - rv: Fully convert enabled_monitors to use list_head as iterator

  * i40e driver is triggering VF resets on every link state change
    (LP: #2130552)
    - i40e: avoid redundant VF link state updates

  * kernel crash on bootup for some arm64 machines (LP: #2129770)
    - KVM: arm64: Guard PMSCR_EL1 initialization with SPE presence check

  * CVE-2025-40018
    - ipvs: Defer ip_vs_ftp unregister during netns cleanup

 -- Manuel Diewald <email address hidden> Fri, 14 Nov 2025 17:53:03 +0100

Changed in linux (Ubuntu Resolute):
status: Triaged → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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-bluefield-v2 verification-needed-noble-linux-bluefield
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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-nvidia-6.17-v2 verification-needed-noble-linux-nvidia-6.17
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-intel/6.17.0-1006.6 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-questing-linux-intel' to 'verification-done-questing-linux-intel'. If the problem still exists, change the tag 'verification-needed-questing-linux-intel' to 'verification-failed-questing-linux-intel'.

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-questing-linux-intel-v2 verification-needed-questing-linux-intel
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-hwe-6.17/6.17.0-14.14~24.04.1 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-hwe-6.17' to 'verification-done-noble-linux-hwe-6.17'. If the problem still exists, change the tag 'verification-needed-noble-linux-hwe-6.17' to 'verification-failed-noble-linux-hwe-6.17'.

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-hwe-6.17-v2 verification-needed-noble-linux-hwe-6.17
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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-6.17-v2 verification-needed-noble-linux-azure-6.17
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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-6.17-v2 verification-needed-noble-linux-azure-fde-6.17
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gcp-6.17/6.17.0-1007.7~24.04.1 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-gcp-6.17' to 'verification-done-noble-linux-gcp-6.17'. If the problem still exists, change the tag 'verification-needed-noble-linux-gcp-6.17' to 'verification-failed-noble-linux-gcp-6.17'.

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-gcp-6.17-v2 verification-needed-noble-linux-gcp-6.17
Revision history for this message
Stefan Bader (smb) wrote :

The many verification requests feel like tooling going wrong. According to sub-tasks this has been released already. But 6.17 backports into noble list them as it is the first public upload for them.

tags: added: verification-done-noble-linux-hwe-6.17
removed: verification-needed-noble-linux-hwe-6.17
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-oracle-6.17/6.17.0-1007.7~24.04.1 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-oracle-6.17' to 'verification-done-noble-linux-oracle-6.17'. If the problem still exists, change the tag 'verification-needed-noble-linux-oracle-6.17' to 'verification-failed-noble-linux-oracle-6.17'.

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-oracle-6.17-v2 verification-needed-noble-linux-oracle-6.17
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

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

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-nvidia-tegra-v2 verification-needed-noble-linux-nvidia-tegra
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.