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 1609607 - [whql][netkvm]Job named NDISTest6.5-InvalidPackets failed with mq in win8-32
Summary: [whql][netkvm]Job named NDISTest6.5-InvalidPackets failed with mq in win8-32
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Amnon Ilan
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1248873
Blocks: 1288337
TreeView+ depends on / blocked
 
Reported: 2018-07-30 03:05 UTC by xiagao
Modified: 2018-08-13 03:16 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1248873
Environment:
Last Closed: 2018-08-13 03:16:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
hck log (2.06 MB, application/x-gzip)
2018-07-30 03:30 UTC, xiagao
no flags Details
I am confused. Attached log shows that Invalid Packets test passes... (126.88 KB, image/png)
2018-07-30 06:31 UTC, Yvugenfi@redhat.com
no flags Details
all logs. (70.71 KB, image/png)
2018-07-30 07:00 UTC, xiagao
no flags Details
update another hck log (2.11 MB, application/zip)
2018-07-30 09:03 UTC, xiagao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2609 0 None None None 2018-07-30 03:05:23 UTC

Comment 3 xiagao 2018-07-30 03:11:51 UTC
steps are same with comment#0;

packages info:
qemu-kvm-rhev-2.12.0-8.el7.x86_64
kernel-3.10.0-926.el7.x86_64
virtio-win-prewhql-157
seabios-bin-1.11.0-2.el7.noarch

Can reproduce in virtio-win-prewhql-151 and virtio-win-prewhql-144.
So it's not a regression.

Comment 4 xiagao 2018-07-30 03:30:59 UTC
Created attachment 1471409 [details]
hck log

Comment 5 Yvugenfi@redhat.com 2018-07-30 06:17:45 UTC
Why this bug is a clone?

According to https://bugzilla.redhat.com/show_bug.cgi?id=1248873#c9 , #1248873 was fixed.

Are you should it is not a regression, did you compare to latest released version?

>>>>
Hello Yan,

Rerun the test case NDIS6.5 - InvalidPackets passed with multiqueue on build 111.  -win8.1_32 

Rerun the test case NDIS6.5 - InvalidPackets passed with multiqueue on build 111.  -win10_64 


Best Regards!
Peixiu Hou
>>>>

Comment 7 Yvugenfi@redhat.com 2018-07-30 06:31:59 UTC
Created attachment 1471419 [details]
I am confused. Attached log shows that Invalid Packets test passes...

I am confused. Attached log shows that Invalid Packets test passes...

Comment 8 xiagao 2018-07-30 06:59:00 UTC
(In reply to Yan Vugenfirer from comment #7)
> Created attachment 1471419 [details]
> I am confused. Attached log shows that Invalid Packets test passes...
> 
> I am confused. Attached log shows that Invalid Packets test passes...

That's because I run three times,two failed with mq and one pass without mq.

Comment 9 xiagao 2018-07-30 07:00:47 UTC
Created attachment 1471423 [details]
all logs.

Could you see all logs?

Comment 10 Yvugenfi@redhat.com 2018-07-30 07:18:49 UTC
(In reply to xiagao from comment #9)
> Created attachment 1471423 [details]
> all logs.
> 
> Could you see all logs?

I don't have failed results in the attached package.

Comment 11 xiagao 2018-07-30 09:03:10 UTC
Created attachment 1471462 [details]
update another hck log

I update one again, pls have a check.

Test result:
build 111 with mq,hit this issue.
build 145(released version of rhel7.5) with mq,hit it.
build 157 in win8.1-32 with mq,pass
build 157 without mq,pass

Comment 12 xiagao 2018-07-30 09:12:53 UTC
(In reply to xiagao from comment #11)
> Created attachment 1471462 [details]
> update another hck log
> 
> I update one again, pls have a check.
> 
> Test result:
> build 111 with mq,hit this issue.
> build 145(released version of rhel7.5) with mq,hit it.
> build 157 in win8.1-32 with mq,pass
> build 157 without mq,pass

I disabled netfilter on the bridge already in the test host.

# sysctl -a | grep bridge
net.bridge.bridge-nf-call-arptables = 0
net.bridge.bridge-nf-call-ip6tables = 0
net.bridge.bridge-nf-call-iptables = 0
net.bridge.bridge-nf-filter-pppoe-tagged = 0
net.bridge.bridge-nf-filter-vlan-tagged = 0
net.bridge.bridge-nf-pass-vlan-input-dev = 0

Comment 13 Yvugenfi@redhat.com 2018-07-30 13:19:32 UTC
Current failure:

Error 7/30/2018 11:46:41.670 AM 8 total breakpoints were hit in the protocol driver while this test was executing 
File:    Line: 0 
Error Type:   WIN32 
Error Code:   0x88888 
Error Text:   Error 0x00088888 
Message 7/30/2018 11:46:41.680 AM NDISTest Protocol driver breakpoints are usually hit when a serious error is detected. Please investigate and fix the issue causing the break to solve this failure. 
Message 7/30/2018 11:46:41.683 AM There were 2 unique breakpoints hit: 
Message 7/30/2018 11:46:41.687 AM Breakpoint Summary
NDISTest Source File	Line	Hit Count	Message	
ndistestheadermodule.cpp	696	20	CNDTNDISTestHeaderModule::OnPacketListsIn: Dropped indications, Expected 1289 but received 1483 
	
ndistestheadermodule.cpp	671	8	CNDTNDISTestHeaderModule::OnPacketListsIn: Out of order indication, Expected 29 but received 20

Comment 14 Sameeh Jubran 2018-08-05 10:04:11 UTC
(In reply to xiagao from comment #11)
> Created attachment 1471462 [details]
> update another hck log
> 
> I update one again, pls have a check.
> 
> Test result:
> build 111 with mq,hit this issue.
> build 145(released version of rhel7.5) with mq,hit it.
> build 157 in win8.1-32 with mq,pass
> build 157 without mq,pass

I am very confused. According to the comment above in build 157 the test passes with no issues. When does it fail? 

What about build 159?

Comment 15 xiagao 2018-08-06 06:06:37 UTC
(In reply to Sameeh Jubran from comment #14)
> (In reply to xiagao from comment #11)
> > Created attachment 1471462 [details]
> > update another hck log
> > 
> > I update one again, pls have a check.
> > 
> > Test result:
> > build 111 with mq,hit this issue.
> > build 145(released version of rhel7.5) with mq,hit it.
> > build 157 in win8.1-32 with mq,pass
> > build 157 without mq,pass
> 
> I am very confused. According to the comment above in build 157 the test
> passes with no issues. When does it fail? 

The point is for win8-32 without mq,the result is pass. With mq,the result is fail.

> 
> What about build 159?
Hit the same issue.

But, if I set all network card's txqueuelen value  with 8196 on host, I test five times, failed once.

Comment 16 Yvugenfi@redhat.com 2018-08-06 07:16:59 UTC
(In reply to xiagao from comment #15)
> (In reply to Sameeh Jubran from comment #14)
> > (In reply to xiagao from comment #11)
> > > Created attachment 1471462 [details]
> > > update another hck log
> > > 
> > > I update one again, pls have a check.
> > > 
> > > Test result:
> > > build 111 with mq,hit this issue.
> > > build 145(released version of rhel7.5) with mq,hit it.
> > > build 157 in win8.1-32 with mq,pass
> > > build 157 without mq,pass
> > 
> > I am very confused. According to the comment above in build 157 the test
> > passes with no issues. When does it fail? 
> 
> The point is for win8-32 without mq,the result is pass. With mq,the result
> is fail.
> 
> > 
> > What about build 159?
> Hit the same issue.
> 
> But, if I set all network card's txqueuelen value  with 8196 on host, I test
> five times, failed once.

Can you check statistics on the host: packets rx\tx\dropped and compare it to the test statistics (the test should show how much packets it sent)?

Comment 17 xiagao 2018-08-07 05:26:05 UTC
(In reply to Yan Vugenfirer from comment #16)
> (In reply to xiagao from comment #15)
> > (In reply to Sameeh Jubran from comment #14)
> > > (In reply to xiagao from comment #11)
> > > > Created attachment 1471462 [details]
> > > > update another hck log
> > > > 
> > > > I update one again, pls have a check.
> > > > 
> > > > Test result:
> > > > build 111 with mq,hit this issue.
> > > > build 145(released version of rhel7.5) with mq,hit it.
> > > > build 157 in win8.1-32 with mq,pass
> > > > build 157 without mq,pass
> > > 
> > > I am very confused. According to the comment above in build 157 the test
> > > passes with no issues. When does it fail? 
> > 
> > The point is for win8-32 without mq,the result is pass. With mq,the result
> > is fail.
> > 
> > > 
> > > What about build 159?
> > Hit the same issue.
> > 
> > But, if I set all network card's txqueuelen value  with 8196 on host, I test
> > five times, failed once.
> 
> Can you check statistics on the host: packets rx\tx\dropped and compare it
> to the test statistics (the test should show how much packets it sent)?

As beaker host is reinstalled, I installed two new guests in it to reproduce this issue with build 157/159,but didn't reproduce it. :(
Tried 5 times.

Comment 18 Sameeh Jubran 2018-08-07 08:28:04 UTC
(In reply to xiagao from comment #17)
> (In reply to Yan Vugenfirer from comment #16)
> > (In reply to xiagao from comment #15)
> > > (In reply to Sameeh Jubran from comment #14)
> > > > (In reply to xiagao from comment #11)
> > > > > Created attachment 1471462 [details]
> > > > > update another hck log
> > > > > 
> > > > > I update one again, pls have a check.
> > > > > 
> > > > > Test result:
> > > > > build 111 with mq,hit this issue.
> > > > > build 145(released version of rhel7.5) with mq,hit it.
> > > > > build 157 in win8.1-32 with mq,pass
> > > > > build 157 without mq,pass
> > > > 
> > > > I am very confused. According to the comment above in build 157 the test
> > > > passes with no issues. When does it fail? 
> > > 
> > > The point is for win8-32 without mq,the result is pass. With mq,the result
> > > is fail.
> > > 
> > > > 
> > > > What about build 159?
> > > Hit the same issue.
> > > 
> > > But, if I set all network card's txqueuelen value  with 8196 on host, I test
> > > five times, failed once.
> > 
> > Can you check statistics on the host: packets rx\tx\dropped and compare it
> > to the test statistics (the test should show how much packets it sent)?
> 
> As beaker host is reinstalled, I installed two new guests in it to reproduce
> this issue with build 157/159,but didn't reproduce it. :(
> Tried 5 times.

So it doesn't reproduce anymore with the new host?
Which version is the new host?
Did you use a newer qemu version aswel?

Comment 19 xiagao 2018-08-07 10:07:42 UTC
(In reply to Sameeh Jubran from comment #18)
> (In reply to xiagao from comment #17)
> > (In reply to Yan Vugenfirer from comment #16)
> > > (In reply to xiagao from comment #15)
> > > > (In reply to Sameeh Jubran from comment #14)
> > > > > (In reply to xiagao from comment #11)
> > > > > > Created attachment 1471462 [details]
> > > > > > update another hck log
> > > > > > 
> > > > > > I update one again, pls have a check.
> > > > > > 
> > > > > > Test result:
> > > > > > build 111 with mq,hit this issue.
> > > > > > build 145(released version of rhel7.5) with mq,hit it.
> > > > > > build 157 in win8.1-32 with mq,pass
> > > > > > build 157 without mq,pass
> > > > > 
> > > > > I am very confused. According to the comment above in build 157 the test
> > > > > passes with no issues. When does it fail? 
> > > > 
> > > > The point is for win8-32 without mq,the result is pass. With mq,the result
> > > > is fail.
> > > > 
> > > > > 
> > > > > What about build 159?
> > > > Hit the same issue.
> > > > 
> > > > But, if I set all network card's txqueuelen value  with 8196 on host, I test
> > > > five times, failed once.
> > > 
> > > Can you check statistics on the host: packets rx\tx\dropped and compare it
> > > to the test statistics (the test should show how much packets it sent)?
> > 
> > As beaker host is reinstalled, I installed two new guests in it to reproduce
> > this issue with build 157/159,but didn't reproduce it. :(
> > Tried 5 times.
> 
> So it doesn't reproduce anymore with the new host?
run seven times, didn't reproduce. 

> Which version is the new host?
KERNEL: 3.10.0-931.el7.x86_64
QEMU: qemu-kvm-rhev-2.12.0-9.el7.x86_64

> Did you use a newer qemu version aswel?
yes,the latest one.

Comment 20 xiagao 2018-08-13 03:16:34 UTC
Test it in the new host with build 160.The result is pass.
So close this bug.


Note You need to log in before you can comment on or make changes to this bug.