ubuntu_kernel_selftests / net:gro.sh fails sometimes on 5.15 / 5.19 amd64/arm64

Bug #1959587 reported by Krzysztof Kozlowski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
New
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Seen only from time to time, e.g. d2021.10.26/jammy/linux-realtime/5.15.0-1004.4/ on gonzo.amd64:
-----
23:34:02 DEBUG| [stdout] # selftests: net: gro.sh
23:34:02 DEBUG| [stdout] # running test ipv4 data
23:34:02 DEBUG| [stdout] # Expected {200 }, Total 1 packets
23:34:02 DEBUG| [stdout] # Received {200 }, Total 1 packets.
23:34:02 DEBUG| [stdout] # Expected {150 }, Total 1 packets
23:34:02 DEBUG| [stdout] # Received {150 }, Total 1 packets.
23:34:02 DEBUG| [stdout] # Expected {50 100 }, Total 2 packets
23:34:02 DEBUG| [stdout] # Received {50 100 }, Total 2 packets.
23:34:02 DEBUG| [stdout] # running test ipv4 ack
23:34:03 DEBUG| [stdout] # Expected {0 0 0 }, Total 3 packets
23:34:03 DEBUG| [stdout] # Received {0 0 0 }, Total 3 packets.
23:34:03 DEBUG| [stdout] # running test ipv4 flags
23:34:04 DEBUG| [stdout] # Expected {300 200 }, Total 2 packets
23:34:04 DEBUG| [stdout] # Received {300 200 }, Total 2 packets.
23:34:04 DEBUG| [stdout] # Expected {200 0 200 }, Total 3 packets
23:34:04 DEBUG| [stdout] # Received {200 0 200 }, Total 3 packets.
23:34:04 DEBUG| [stdout] # Expected {200 0 200 }, Total 3 packets
23:34:04 DEBUG| [stdout] # Received {200 0 200 }, Total 3 packets.
23:34:04 DEBUG| [stdout] # Expected {200 0 200 }, Total 3 packets
23:34:04 DEBUG| [stdout] # Received {200 0 200 }, Total 3 packets.
23:34:04 DEBUG| [stdout] # running test ipv4 tcp
23:34:04 DEBUG| [stdout] # Expected {100 100 }, Total 2 packets
23:34:05 DEBUG| [stdout] # Received {100 100 }, Total 2 packets.
23:34:05 DEBUG| [stdout] # Expected {100 100 }, Total 2 packets
23:34:05 DEBUG| [stdout] # Received {100 100 }, Total 2 packets.
23:34:05 DEBUG| [stdout] # Expected {200 100 100 100 }, Total 4 packets
23:34:05 DEBUG| [stdout] # Received {200 100 100 100 }, Total 4 packets.
23:34:05 DEBUG| [stdout] # Expected {200 100 }, Total 2 packets
23:34:05 DEBUG| [stdout] # Received {200 100 }, Total 2 packets.
23:34:05 DEBUG| [stdout] # running test ipv4 ip
23:34:05 DEBUG| [stdout] # Expected {100 100 }, Total 2 packets
23:34:06 DEBUG| [stdout] # Received {100 100 }, Total 2 packets.
23:34:06 DEBUG| [stdout] # Expected {100 100 }, Total 2 packets
23:34:06 DEBUG| [stdout] # Received {100 100 }, Total 2 packets.
23:34:06 DEBUG| [stdout] # Expected {100 100 }, Total 2 packets
23:34:07 DEBUG| [stdout] # Received {100 100 }, Total 2 packets.
23:34:07 DEBUG| [stdout] # Expected {100 100 100 }, Total 3 packets
23:34:09 DEBUG| [stdout] # Received {100 100 100 }, Total 3 packets.
23:34:09 DEBUG| [stdout] # Expected {100 100 }, Total 2 packets
23:34:11 DEBUG| [stdout] # Received {100 100 }, Total 2 packets.
23:34:11 DEBUG| [stdout] # running test ipv4 large
23:34:11 DEBUG| [stdout] # Expected {65495 919 }, Total 2 packets
23:34:12 DEBUG| [stdout] # Received {65495 919 }, Total 2 packets.
23:34:12 DEBUG| [stdout] # Expected {64576 920 920 }, Total 3 packets
23:34:12 DEBUG| [stdout] # Received {12108 [!=64576]53388 [!=920]920 }, Total 3 packets.
23:34:12 DEBUG| [stdout] # ./gro: incorrect packet geometry
23:34:12 DEBUG| [stdout] # Expected {65495 919 }, Total 2 packets
23:34:12 DEBUG| [stdout] # Received {65495 919 }, Total 2 packets.
23:34:12 DEBUG| [stdout] # Expected {64576 920 920 }, Total 3 packets
23:34:12 DEBUG| [stdout] # Received {16144 [!=64576]49352 [!=920]920 }, Total 3 packets.
23:34:12 DEBUG| [stdout] # ./gro: incorrect packet geometry
23:34:12 DEBUG| [stdout] # Expected {65495 919 }, Total 2 packets
23:34:13 DEBUG| [stdout] # Received {65495 919 }, Total 2 packets.
23:34:13 DEBUG| [stdout] # Expected {64576 920 920 }, Total 3 packets
23:34:13 DEBUG| [stdout] # Received {32288 [!=64576]33208 [!=920]920 }, Total 3 packets.
23:34:13 DEBUG| [stdout] # ./gro: incorrect packet geometry
23:34:13 DEBUG| [stdout] # running test ipv6 data
23:34:13 DEBUG| [stdout] # Expected {200 }, Total 1 packets
23:34:14 DEBUG| [stdout] # Received {200 }, Total 1 packets.
23:34:14 DEBUG| [stdout] # Expected {150 }, Total 1 packets
23:34:14 DEBUG| [stdout] # Received {150 }, Total 1 packets.
23:34:14 DEBUG| [stdout] # Expected {50 100 }, Total 2 packets
23:34:14 DEBUG| [stdout] # Received {50 100 }, Total 2 packets.
23:34:14 DEBUG| [stdout] # running test ipv6 ack
23:34:14 DEBUG| [stdout] # Expected {0 0 0 }, Total 3 packets
23:34:15 DEBUG| [stdout] # Received {0 0 0 }, Total 3 packets.
23:34:15 DEBUG| [stdout] # running test ipv6 flags
23:34:15 DEBUG| [stdout] # Expected {300 200 }, Total 2 packets
23:34:16 DEBUG| [stdout] # Received {300 200 }, Total 2 packets.
23:34:16 DEBUG| [stdout] # Expected {200 0 200 }, Total 3 packets
23:34:16 DEBUG| [stdout] # Received {200 0 200 }, Total 3 packets.
23:34:16 DEBUG| [stdout] # Expected {200 0 200 }, Total 3 packets
23:34:16 DEBUG| [stdout] # Received {200 0 200 }, Total 3 packets.
23:34:16 DEBUG| [stdout] # Expected {200 0 200 }, Total 3 packets
23:34:16 DEBUG| [stdout] # Received {200 0 200 }, Total 3 packets.
23:34:16 DEBUG| [stdout] # running test ipv6 tcp
23:34:16 DEBUG| [stdout] # Expected {100 100 }, Total 2 packets
23:34:16 DEBUG| [stdout] # Received {100 100 }, Total 2 packets.
23:34:16 DEBUG| [stdout] # Expected {100 100 }, Total 2 packets
23:34:16 DEBUG| [stdout] # Received {100 100 }, Total 2 packets.
23:34:16 DEBUG| [stdout] # Expected {200 100 100 100 }, Total 4 packets
23:34:16 DEBUG| [stdout] # Received {200 100 100 100 }, Total 4 packets.
23:34:16 DEBUG| [stdout] # Expected {200 100 }, Total 2 packets
23:34:16 DEBUG| [stdout] # Received {200 100 }, Total 2 packets.
23:34:16 DEBUG| [stdout] # running test ipv6 ip
23:34:17 DEBUG| [stdout] # Expected {100 100 }, Total 2 packets
23:34:17 DEBUG| [stdout] # Received {100 100 }, Total 2 packets.
23:34:17 DEBUG| [stdout] # Expected {100 100 }, Total 2 packets
23:34:17 DEBUG| [stdout] # Received {100 100 }, Total 2 packets.
23:34:17 DEBUG| [stdout] # Expected {200 100 }, Total 2 packets
23:34:17 DEBUG| [stdout] # Received {200 100 }, Total 2 packets.
23:34:17 DEBUG| [stdout] # running test ipv6 large
23:34:18 DEBUG| [stdout] # Expected {65475 899 }, Total 2 packets
23:34:18 DEBUG| [stdout] # Received {65475 899 }, Total 2 packets.
23:34:18 DEBUG| [stdout] # Expected {64576 900 900 }, Total 3 packets
23:34:18 DEBUG| [stdout] # Received {16144 [!=64576]49332 [!=900]900 }, Total 3 packets.
23:34:18 DEBUG| [stdout] # ./gro: incorrect packet geometry
23:34:18 DEBUG| [stdout] # Expected {65475 899 }, Total 2 packets
23:34:19 DEBUG| [stdout] # Received {65475 899 }, Total 2 packets.
23:34:19 DEBUG| [stdout] # Expected {64576 900 900 }, Total 3 packets
23:34:19 DEBUG| [stdout] # Received {64576 900 900 }, Total 3 packets.
23:34:19 DEBUG| [stdout] # failed tests: ipv4_large. Please see log.txt for more logs
23:34:19 DEBUG| [stdout] not ok 1 selftests: net: gro.sh # exit=1
-----

Not possible to reproduce manually on akis.amd64 or avoton instances.

tags: added: 5.15 jammy realtime
summary: - ubuntu_kernel_selftests/net:gro.sh fails sometimes on Jammy/realtime
+ ubuntu_kernel_selftests:net:gro.sh fails sometimes on Jammy/realtime
v5.15 amd64
summary: - ubuntu_kernel_selftests:net:gro.sh fails sometimes on Jammy/realtime
+ ubuntu_kernel_selftests / net:gro.sh fails sometimes on Jammy/realtime
v5.15 amd64
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1959587

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote : Re: ubuntu_kernel_selftests / net:gro.sh fails sometimes on Jammy/realtime v5.15 amd64

This can be found on J-hwe-5.19.0-1020.21~22.04.1 ARM64 starmie-kernel as well.

Po-Hsu Lin (cypressyew)
summary: - ubuntu_kernel_selftests / net:gro.sh fails sometimes on Jammy/realtime
- v5.15 amd64
+ ubuntu_kernel_selftests / net:gro.sh fails sometimes on 5.15 / 5.19
+ amd64/arm64
tags: added: 5.19 amd64 arm64 sru-20230227 ubuntu-kernel-selftests
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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