HLK glitchfreedevice case failure for breakpoints were hit

Baowen Zheng 25 Reputation points
2023-03-22T09:55:52.36+00:00

Hi windows:

currently we are working on miniport driver HLK tests. now we are blocked on the test case named as glitchfreedevice.

the error reported as:

30 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 2 unique breakpoints hit:

Breakpoint SummaryNDISTest Source FileLineHit CountMessagendistestheadermodule.cpp69630CNDTNDISTestHeaderModule::OnPacketListsIn: Dropped indications, Expected 59 but received 60ndistestheadermodule.cpp67130CNDTNDISTestHeaderModule::OnPacketListsIn: Out of order indication, Expected 61 but received 59could you please help to clarify what does the error means and how can we fix this issue?

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,371 questions
Windows Network
Windows Network
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.Network: A group of devices that communicate either wirelessly or via a physical connection.
648 questions
Windows Hardware Performance
Windows Hardware Performance
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.Hardware Performance: Delivering / providing hardware or hardware systems or adjusting / adapting hardware or hardware systems.
1,542 questions
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Limitless Technology 43,931 Reputation points
    2023-03-22T14:14:15.9533333+00:00

    Hello there,

    You should check whether the test requires a special configuration and if it does, verify that all special configuration requirements are met.

    Some Windows HLK tests require additional files that are not included in the Windows HLK because of size or security reasons. Windows HLK Studio denotes these tests as requiring special configuration. These tests fail if the supplemental data is not installed.

    Before you run the test, complete the test setup as described in the test requirements. The content in this section describes the LAN (Ethernet) testing prerequisites that you should complete before testing your network adapter using the Windows Hardware Lab Kit (Windows HLK). https://learn.microsoft.com/en-us/windows-hardware/test/hlk/testref/lan-testing-prerequisites

    Troubleshooting Windows HLK Test Failures https://learn.microsoft.com/en-us/windows-hardware/test/hlk/user/troubleshooting-windows-hlk-test-failures#specconfig

    Hope this resolves your Query !!

    --If the reply is helpful, please Upvote and Accept it as an answer–

  2. Baowen Zheng 25 Reputation points
    2023-04-06T11:40:40.13+00:00

    Hi Windows: can anyone help to analyze this failure? since it has blocked us for a long this and we have no idea to pass this case. thanks

    0 comments
  3. E K 0 Reputation points
    2023-08-29T13:40:00.58+00:00

    Hello Baowen,

    We had the same issue with this test.

    For us , the problem was related to the not-so-optimized send/receive paths.

    Suggestions :

    1. Try tracing packets (NBs, NBLs, BDbufferDescriptor num frm hw..) to see if any order inconsistency occurs(for instance BD 4,5,6..next 9,11 or similar)
    2. Probably you use double linked lists for busy/free controller blocks. Check them if they correctly remove/add the new items(to/from head/tail). For instance ,in case of a failure/empty item, the removed item should be added to head again not to tail(if it is taken form the head in the first place of course)

    Possible cause :

    First, the sample driver code is for a virtual(not actual hw) NIC. there are part related to the hw-simulation.

    Besides , we use our old driver(ndis5) driver code as start point for the new one.

    As you can guess, the combination can cause troubles as it did for us.

    It was not a big deal to combine/adapt and make it work. However for the test it is not enough that it works on basic level. As the packet umbers and transport speed increase issues arise.

    Note :

    Glitchfree test is related to number of NBL indication pro dpc , be sure that you get the number from ReceiveThrottleParameters of MiniportInterruptDPC and make the dpc return after that count.

    I hope those help.

    A request :It would be nice if you consider taking a look at my question and sharing any ideas .

    https://learn.microsoft.com/en-us/answers/questions/1354615/is-wake-on-lan-support-mandatory-for-ndis-miniport

    Best Wishes

    Elif

    0 comments