Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Home NTDEV
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Why my Test case Failed for logo certification test ?

vinay_kpvinay_kp Member Posts: 182
When i run " NDISTest 6.5 ShortPackets " Test for windows hardware certification process ,my test failed . I took log file .. but i got some error like this :

Shortpacket.htm log file ::

*************************************************************************
Send/Receive 40 packets from my Virtual Network Driver to myVirtual Network Driver, with packetsize 45.

CommunicationHelper::StartReceive
- Name: SuppDeviceSimpleCommHelper
- Type: SimpleCommunicationHelper
- Traffic Manager Type: NDT_SIMPLE_TRAFFIC_MGR
- Receive Process Mech: NDT_PROCESS_RECEIVE_AT_PASSIVE
- Configured NetBufferModuleStack:
- [1] NDT_SIMPLE_NDISTEST_PAYLOAD_MODULE
- [2] NDT_NDISTEST_HEADER_MODULE
- [3] NDT_LLC_SNAP_HEADER_MODULE
- [4] NDT_ETHERNET_MEDIA_HEADER_MODULE
- STATUS: NDIS_STATUS_SUCCESS

CommunicationHelper::StartSend
- Name: TestDeviceSimpleCommHelper
- Type: SimpleCommunicationHelper
- Traffic Manager Type: NDT_SIMPLE_TRAFFIC_MGR
- Send Mechanism: NDT_SEND_AT_PASSIVE
- Send Complete Mech: NDT_VERIFY_SEND_COMPLETE_AT_PASSIVE
- NDIS Send Flags: 0
- Send Latency (ms): 0
- Preallocated NBL Count: 2
- Configured NetBufferModuleStack:
- [0] NDT_SIMPLE_NB_ALLOCATOR_MODULE
- [1] NDT_SIMPLE_NDISTEST_PAYLOAD_MODULE
- [2] NDT_NDISTEST_HEADER_MODULE
- [3] NDT_LLC_SNAP_HEADER_MODULE
- [4] NDT_ETHERNET_MEDIA_HEADER_MODULE
- STATUS: NDIS_STATUS_SUCCESS

EndPoint::WaitForSendsToComplete
- Name: TestDeviceSimpleCommHelper_EndPoint
- Timeout (ms): 300000
EndPoint::StopReceive
- Name: SuppDeviceSimpleCommHelper_EndPoint
- Timeout (ms): 5000
EndPoint::GetSendResults
- Name: TestDeviceSimpleCommHelper_EndPoint
EndPoint::GetReceiveResults
- Name: SuppDeviceSimpleCommHelper_EndPoint
EndPoint::GetReceiveResults
- Name: SuppDeviceSimpleCommHelper_EndPoint
Packets sent: 40 (20 NBLs * 2 NBs/NBL)


Send Statistics

TotalNBLsSent 20
TotalCallsToSend 10
TotalNBLsSendCompleted 20
TotalNBLSendsSuccessful 20


Packets Received: 20
50013 Received less than the expected percentage of packets sent.
We expected 32 packets (80 percent of 40 packets sent).


NDISTest Payload Receive Statistics

TotalNetBuffersAccepted 20
TotalNetBuffersCorrupted 0
TotalBadlyPaddedPacketsReceived 20


50014 The miniport did not correctly pad all short packets. 20 incorrect packets.
This failure is hit for one of two reasons:

1. The short packets being sent aren't padded up to 60 bytes
2. The padding used isn't a repeating pattern of the same character
Check the NDISTest server (server.htm) log file to see if NDISTest protocol breakpoints were hit to determine the root cause.


NDISTest Header Receive Statistics

TotalNetBuffersReceived 20
TotalNetBuffersAccepted 20
TotalNetBuffersCorrupted 0
OutOfOrderNetBuffersReceived 0
DroppedNetBufferBursts 0
DuplicateNetBuffersReceived 0




Traffic Manager Receive Statistics :


TotalReceiveIndications 20
TotalReceiveIndicationsWithResources 20
TotalRecognizedRecvNBLs 20
TotalRecognizedRecvNBLsWithResources 20

EndPoint::CloseCommunicationChannel
- Name: TestDeviceSimpleCommHelper_EndPoint
EndPoint::CloseCommunicationChannel
- Name: SuppDeviceSimpleCommHelper_EndPoint

*******************************************************************

and server.htm log :

88888 540 total breakpoints were hit in the protocol driver while this test was executing .

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.
There were 1 unique breakpoints hit:


NDISTest Source File Line HIT COUNT message



ndistestpacket.cpp 451 540


Badly padded packet in the NetBuffer received. Ethernet Packet size is less than the minimum size allowed.
Corrupt MDL = 88F24DE0 , Net Buffer List = 890C6018
Expected Size of packet = 60, Actual Size of packet received = 45

Comments

  • Tim_RobertsTim_Roberts Member - All Emails Posts: 13,605
    [email protected] wrote:
    > When i run " NDISTest 6.5 ShortPackets " Test for windows hardware certification process ,my test failed . I took log file .. but i got some error like this :

    And did you chase down what it said? It says it sent 20 NBLs with 2 NBs
    per NBL, but it only got 20 packets, Are you handling multiple NBs in
    each NBL?

    --
    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • vinay_kpvinay_kp Member Posts: 182
    How to handle multiple NBs in each NBL?
  • Tim_RobertsTim_Roberts Member - All Emails Posts: 13,605
    [email protected] wrote:
    > How to handle multiple NBs in each NBL?

    I'm not a network guy, so I can't answer this. I assumed that, if you
    had written an NDIS miniport, this concept would mean something to you.

    --
    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.

  • OSR_Community_UserOSR_Community_User Member Posts: 110,217
    Hi vinay0032,

    >50014 The miniport did not correctly pad all short packets. 20 incorrect packets.
    >This failure is hit for one of two reasons:
    >
    >1. The short packets being sent aren't padded up to 60 bytes
    >2. The padding used isn't a repeating pattern of the same character


    Forgive me for being blunt, but it IS the short packet test that fails and this IS a very clear direct and explicit reason for it failing, that directly explains what’s wrong in no uncertain terms. So why aren’t you fixing the broken short packet handling in the code and re-testing?

    Then (maybe) you might need to look at remaining failures in your test report. But don’t post until you’re stuck, as it annoys people freely giving their time to help, if you don’t appear to have even tried to help yourself.

    You might follow up the advice and...

    >Check the NDISTest server (server.htm) log file to see if NDISTest protocol breakpoints were hit to determine the root cause.

    Personally I’d just assume the original miniport coder has not understood a requirement to pad short packets and go straight to the code and fix it.

    Sent from Mail for Windows 10



    From: Tim Roberts
    Sent: 15 October 2015 21:41
    To: Windows System Software Devs Interest List
    Subject: Re: [ntdev] Why my Test case Failed for logo certification test ?


    [email protected] wrote:
    > How to handle multiple NBs in each NBL?

    I'm not a network guy, so I can't answer this. I assumed that, if you
    had written an NDIS miniport, this concept would mean something to you.

    --
    Tim Roberts, [email protected]
    Providenza & Boekelheide, Inc.


    ---
    NTDEV is sponsored by OSR

    Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

    OSR is HIRING!! See http://www.osr.com/careers

    For our schedule of WDF, WDM, debugging and other seminars visit:
    http://www.osr.com/seminars

    To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
  • SangeethaSangeetha Member Posts: 10

    I am also running into this now. Made sure that we are padding the received packets. Do you have a code snippet to pad the packets being sent out from the support machine?

  • Peter_Viscarola_(OSR)Peter_Viscarola_(OSR) Administrator Posts: 8,052
    edited March 3

    You're replying to a post from 2015.

    Seriously, Mr. Sangeetha... Two posts out of two... both necroposts. Both in violation of our beloved forum guidelines. You think I should let you continue posting here? Just asking your opinion.

    Peter

    Peter Viscarola
    OSR
    @OSRDrivers

  • SangeethaSangeetha Member Posts: 10

    Sorry about that, Will start a new thread for all of my same questions

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Writing WDF Drivers 7 Dec 2020 LIVE ONLINE
Internals & Software Drivers 25 Jan 2021 LIVE ONLINE
Developing Minifilters Early 2021 LIVE ONLINE