RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1871330 - [NetKVM] HCK: Offload.Lso test fails on HCK 1903
Summary: [NetKVM] HCK: Offload.Lso test fails on HCK 1903
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: virtio-win
Version: 9.0
Hardware: x86_64
OS: Windows
unspecified
medium
Target Milestone: rc
: 9.0
Assignee: ybendito
QA Contact: leidwang@redhat.com
URL:
Whiteboard:
Depends On: 1946564
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-22 12:10 UTC by ybendito
Modified: 2022-05-17 15:36 UTC (History)
9 users (show)

Fixed In Version: virtio-win-prewhql-0.1-211
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 15:35:26 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2022:3890 0 None None None 2022-05-17 15:36:12 UTC

Description ybendito 2020-08-22 12:10:35 UTC 
Description of problem:
The test fails with high rate when run after Mini6Performance test

Version-Release number of selected component (if applicable):
0.1-189 and earliers

How reproducible:
Sometimes ~70% first run after Mini6Performance
Rerun fails 100%
If the SUT rebooted, the test passes.

The same happens if we run Win8.1 build on 1903 HCK (Win8.1 build always behaves as NDIS 6.30 miniport, Win10 build behaves as 6.80 miniport on 1903).
Comment 1 xiagao 2020-08-26 07:32:36 UTC 
Run Mini6Performance test on hlk-2004 for 16 times, all pass.
win10 iso:
en_windows_10_business_editions_version_2004_updated_may_2020_x64_dvd_aa8db2cc.iso

So this issue didn't reproduce on hlk-2004

I will have a try on hlk-1903.
Comment 2 xiagao 2020-09-07 10:06:45 UTC 
(In reply to xiagao from comment #1)
> Run Mini6Performance test on hlk-2004 for 16 times, all pass.
> win10 iso:
> en_windows_10_business_editions_version_2004_updated_may_2020_x64_dvd_aa8db2c
> c.iso
> 
> So this issue didn't reproduce on hlk-2004
> 
> I will have a try on hlk-1903.


Also didn't reproduce on hlk-1903, run 16 times all pass.
win10 iso:
en_windows_10_business_editions_version_1903_x64_dvd_37200948.iso

hlk-1903 studio version:
10.0.19041.1
Comment 3 ybendito 2020-09-19 14:36:42 UTC 
(In reply to xiagao from comment #2)
> (In reply to xiagao from comment #1)
> > Run Mini6Performance test on hlk-2004 for 16 times, all pass.
> > win10 iso:
> > en_windows_10_business_editions_version_2004_updated_may_2020_x64_dvd_aa8db2c
> > c.iso
> > 
> > So this issue didn't reproduce on hlk-2004
> > 
> > I will have a try on hlk-1903.
> 
> 
> Also didn't reproduce on hlk-1903, run 16 times all pass.
> win10 iso:
> en_windows_10_business_editions_version_1903_x64_dvd_37200948.iso
> 
> hlk-1903 studio version:
> 10.0.19041.1

The problem is with Offload.Lso test, not with Mini6Performance.
Mini6Performance passes, but if Offload.Lso runs after it, the Offload.Lso fails
Comment 4 ybendito 2020-09-19 15:00:42 UTC 
The same problem I see with 2004
Comment 6 xiagao 2020-09-23 09:42:19 UTC 
Can reproduce this bug with win1064(2004) with 189 driver.
After Mini6Performance passed, run Offload.Lso for 14 times and failed 4 times.
Comment 8 ybendito 2021-04-04 20:24:58 UTC 
Typical failure of OffloadLSO test on 2004 is:
"50017", "The offload capability reported by miniport's status indication is unable to support this Test Case"
Looks like the problem can be solved by building the driver with WDK 1903 or 2004, declaring support for NDIS 6.83 and reporting offloads in updated/extended structure.
So the solution will be similar to one of Bug#1894064
Comment 9 leidwang@redhat.com 2021-10-13 01:13:04 UTC 
Tested this job with virtio-win-prewhql-0.1-211 on win1064.After Mini6Performance passed, run Offload.Lso for 11 times and failed 1 times.
Comment 10 Yvugenfi@redhat.com 2021-10-19 08:43:24 UTC 
(In reply to leidwang from comment #9)
> Tested this job with virtio-win-prewhql-0.1-211 on win1064.After
> Mini6Performance passed, run Offload.Lso for 11 times and failed 1 times.

Please provide the logs. Also please check if there was a crash dump saved on the test client.

Thanks.
Comment 13 leidwang@redhat.com 2021-11-02 08:38:40 UTC 
Hi Yan,

Could you reset the DTM? Because the current DTM has passed.Thanks
Comment 14 ybendito 2021-11-03 07:36:44 UTC 
According to comment #8 and comment #9 the problem was solved. If another problem (as described in comment #11) is reproducible please open another BZ and attach HLKX and/or dump file (please do not use screenshots).
Comment 15 leidwang@redhat.com 2021-11-03 07:53:49 UTC 
(In reply to ybendito from comment #14)
> According to comment #8 and comment #9 the problem was solved. If another
> problem (as described in comment #11) is reproducible please open another BZ
> and attach HLKX and/or dump file (please do not use screenshots).

You mean I can set this bz status to verified?
Comment 16 ybendito 2021-11-03 07:55:35 UTC 
(In reply to leidwang from comment #15)
> (In reply to ybendito from comment #14)
> > According to comment #8 and comment #9 the problem was solved. If another
> > problem (as described in comment #11) is reproducible please open another BZ
> > and attach HLKX and/or dump file (please do not use screenshots).
> 
> You mean I can set this bz status to verified?

Yes
Comment 17 leidwang@redhat.com 2021-11-03 07:58:23 UTC 
(In reply to ybendito from comment #16)
> (In reply to leidwang from comment #15)
> > (In reply to ybendito from comment #14)
> > > According to comment #8 and comment #9 the problem was solved. If another
> > > problem (as described in comment #11) is reproducible please open another BZ
> > > and attach HLKX and/or dump file (please do not use screenshots).
> > 
> > You mean I can set this bz status to verified?
> 
> Yes

Okay, if so, I will set this bz to VERIFIED.
If I hit the issue again, I will file a new bz for comment11.
Thanks!
Comment 21 errata-xmlrpc 2022-05-17 15:35:26 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: virtio-win), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:3890
Note You need to log in before you can comment on or make changes to this bug.