Bug 584293 - Ethernet-NDIS Test 6.5 "protocol assertion failure (88888)" in WHQL network test for Windows2008
Summary: Ethernet-NDIS Test 6.5 "protocol assertion failure (88888)" in WHQL network t...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: xenpv-win
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Xen Maintainance List
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 518435
TreeView+ depends on / blocked
 
Reported: 2010-04-21 09:46 UTC by Xiaoli Tian
Modified: 2010-11-16 12:46 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 19:29:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
analysis of memory dump file (9.18 KB, text/plain)
2010-04-21 09:46 UTC, Xiaoli Tian
no flags Details
screenshot of BSOD (113.94 KB, image/png)
2010-04-21 09:49 UTC, Xiaoli Tian
no flags Details
NDIS test log (113.14 KB, text/html)
2010-04-22 02:53 UTC, Xiaoli Tian
no flags Details
AddressChange log (132.92 KB, text/html)
2010-04-22 02:55 UTC, Xiaoli Tian
no flags Details
NDIS test log being tested in another time (552.29 KB, text/html)
2010-04-22 08:34 UTC, Xiaoli Tian
no flags Details

Description Xiaoli Tian 2010-04-21 09:46:43 UTC
Created attachment 408032 [details]
analysis of  memory dump file

Description of problem:
Ethernet-NDIS Test 6.5 caused BSOD in WHQL network test for Windows2008.
the screen shot of BSOD and the analysis of memory dump file are attached for 
your reference. 

Version-Release number of selected component (if applicable):
version of Xen-PV Driver:04/12/2010,1.1.0.3
Kenel :kernel-xen-2.6.18-195.el5

How reproducible:
always

Steps to Reproduce:
1.prepare the WHQL test environment
2.install xenpv-win driver
3.start to test "Ethernet-NDIS Test 6.5"
  
Actual results:
BSOD

Expected results:
pass

Additional info:
the screen shot of BSOD and analysis of  memory dump file are attached.

Comment 1 Xiaoli Tian 2010-04-21 09:49:04 UTC
Created attachment 408033 [details]
screenshot of BSOD

Comment 2 Paolo Bonzini 2010-04-21 12:48:43 UTC

*** This bug has been marked as a duplicate of bug 566786 ***

Comment 3 Paolo Bonzini 2010-04-21 12:49:28 UTC
Closed wrong bug.

Do you know what test was running before the crash?  In other words, do you have some kind of log?

Comment 4 Xiaoli Tian 2010-04-22 02:53:51 UTC
Created attachment 408217 [details]
NDIS test log

Comment 5 Xiaoli Tian 2010-04-22 02:55:12 UTC
Created attachment 408218 [details]
AddressChange  log

Comment 6 Xiaoli Tian 2010-04-22 02:57:06 UTC
(In reply to comment #3)
> Closed wrong bug.
> 
> Do you know what test was running before the crash?  In other words, do you
> have some kind of log?    

Hi,Paolo
 the following are some of the failure logs,pls refer to the above attachment about more details:

Verifying the setup configuration for product SKU VER_SUITE_DATACENTER or VER_SUITE_ENTERPRISE
There are sufficient number of processors on this system to run the test pass.
Adapter RedHat PV NIC Driver is deserialized
50018 For running logo tests for devices VER_SUITE_DATACENTER and VER_SUITE_ENTERPRISE skus drivers should use scatter gather DMA
Querying miniport for OID_GEN_MINIPORT_INFO did not return with NDIS_MINIPORT_SG_LIST bit set
50019 For running logo tests for devices VER_SUITE_DATACENTER and VER_SUITE_ENTERPRISE skus drivers should be capable of 64 bit addressing
Querying miniport for OID_GEN_MINIPORT_INFO did not return with NDIS_MINIPORT_64BITS_DMA bit set

thanks
xiaoli

Comment 7 Paolo Bonzini 2010-04-22 07:51:20 UTC
Thanks.  The AddressChange test is probably something in the host.  I usually get 250/250 packets received here.

The 50018 and 50019 failures are known, and we'll have to ask Microsoft for a waiver (bug 534085).

The interesting failure here is:

-------------
2055871060	StartTime:	07:47:25.788
Unexpected Failure Outside of a Test Case or Action
88888 A breakpoint was hit in the protocol driver while this test was executing
	Duration:	00:00:00:00.00
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.
Protocol::DeregisterProtocol
- Name: NDISTestSendProtocol
Protocol::DestroyOpen
- Name: TestBinding
Protocol::DeregisterProtocol
- Name: NDISSupportSendProtocol
Protocol::DestroyOpen
- Name: SupportBinding 
-------------

I never saw anything like that on 2008.

Comment 8 Xiaoli Tian 2010-04-22 08:34:28 UTC
Created attachment 408263 [details]
NDIS test log  being tested in another time


 I don't know why does it have the  interest failure as well,I could upload the failure log of NDIS test 6.5 which was tested on Windows 2008 x86.It seems to have the same failure.
thanks

Comment 9 Paolo Bonzini 2010-04-22 12:05:01 UTC
I see it too now, sorry for the noise.

Comment 10 Paolo Bonzini 2010-05-31 15:33:07 UTC
The reset failure is intermittent, and most likely occurs in the invalidpackages test.  It's visible on WLK 1.5 but not 1.4.

Also, I could reproduce it with the RealTek drivers under both Xen and KVM, so I'm wondering whether it's a bug in NDISTest.

Comment 12 RHEL Program Management 2010-08-09 18:10:43 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 13 Paolo Bonzini 2010-10-06 13:16:49 UTC
Still reproducible with the 1.3.0 drivers.

Doesn't result in a breakpoint (ASSERT or anything) when running under WinDbg, so I'm quite at a loss here.


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