Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - devnp-e1000.so Squelch Test errors : (11 Items)
   
devnp-e1000.so Squelch Test errors  
#nicinfo wm0

shows an increase in the number of errors
...
Squelch Test errors .......
...

Which leads to a failure in the qnet and Tcpip protocols.

Driver devnp-qnet.so vid = 0x8086, did = 0x15b3

NAME = devnp-e1000.so
DESCRIPTION = Driver for Intel 82544 Gigabit Ethernet controllers
DATE = 2015/11 / 30-12: 50: 20-EST
STATE = stable
HOST = gusbuild8
USER = builder
VERSION = 1344
TAGID = PSP_networking_br650_be650SP1

What could be the causes of failures, what could be the recommendations?

Thanks
Re: devnp-e1000.so Squelch Test errors  
Squelch test errors are from the missed packet count register (receive overruns) of the e1000.


On 2018-12-14, 2:21 AM, "Leonid Khait" <community-noreply@qnx.com> wrote:

    #nicinfo wm0
    
    shows an increase in the number of errors
    ...
    Squelch Test errors .......
    ...
    
    Which leads to a failure in the qnet and Tcpip protocols.
    
    Driver devnp-qnet.so vid = 0x8086, did = 0x15b3
    
    NAME = devnp-e1000.so
    DESCRIPTION = Driver for Intel 82544 Gigabit Ethernet controllers
    DATE = 2015/11 / 30-12: 50: 20-EST
    STATE = stable
    HOST = gusbuild8
    USER = builder
    VERSION = 1344
    TAGID = PSP_networking_br650_be650SP1
    
    What could be the causes of failures, what could be the recommendations?
    
    Thanks
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post119357
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com
    

Re: devnp-e1000.so Squelch Test errors  
Sorry my mistake:
 ...
    Driver devnp-e100.so vid = 0x8086, did = 0x15b3
...

So, is it hardware problem or driver e1000 error?

That problem happens too infrequently.

How to solve that, 

Thank you.
Re: devnp-e1000.so Squelch Test errors  
You can try increasing the number of receive buffers with the "receive=nnn" command line option, where nnn can be 
between 64 and 4096. The default used to be 128 receive buffers, so you can try anything higher than that.


On 2018-12-14, 9:01 PM, "Leonid Khait" <community-noreply@qnx.com> wrote:

    Sorry my mistake:
     ...
        Driver devnp-e100.so vid = 0x8086, did = 0x15b3
    ...
    
    So, is it hardware problem or driver e1000 error?
    
    That problem happens too infrequently.
    
    How to solve that, 
    
    Thank you.
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post119359
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com
    

Re: devnp-e1000.so Squelch Test errors  
From the description of the driver, I understand that increasing the file descriptor buffer by "receive=4096" argument 
will not solve the Squelch Test Error increase counter problem. 

Since this counter signals the problem is inside the NIC interface itself: the  overran of its internal FIFO buffer.

Is it so?

---

From devnp-e1000.so Description:
...
The SQE (Squelch Test Errors) counter — one of the fields reported by nicinfo — isn't applicable to devnp-e1000.so, so
 this driver uses it in a non-standard way. You can lose packets because:

    you ran out of descriptors (the NIC was able to buffer the packet, but there was no CPU RAM available)

    or:
    the NIC was unable to buffer the packet because it overran its internal Rx FIFO

Other drivers add the two together, but this driver uses the SQE counter for internal Rx FIFO overruns, which generally 
indicate excessive bus latency, perhaps misconfigured link-level flow control, or even misconfigured Rx FIFO watermarks.

...
Re: devnp-e1000.so Squelch Test errors  
Yes, it is so, as you can see from the description that you posted as well.


On 2019-04-06, 12:09 AM, "Leonid Khait" <community-noreply@qnx.com> wrote:

    From the description of the driver, I understand that increasing the file descriptor buffer by "receive=4096" 
argument will not solve the Squelch Test Error increase counter problem. 
    
    Since this counter signals the problem is inside the NIC interface itself: the  overran of its internal FIFO buffer.

    
    Is it so?
    
    ---
    
    From devnp-e1000.so Description:
    ...
    The SQE (Squelch Test Errors) counter — one of the fields reported by nicinfo — isn't applicable to devnp-e1000.so
, so this driver uses it in a non-standard way. You can lose packets because:
    
        you ran out of descriptors (the NIC was able to buffer the packet, but there was no CPU RAM available)
    
        or:
        the NIC was unable to buffer the packet because it overran its internal Rx FIFO
    
    Other drivers add the two together, but this driver uses the SQE counter for internal Rx FIFO overruns, which 
generally indicate excessive bus latency, perhaps misconfigured link-level flow control, or even misconfigured Rx FIFO 
watermarks.
    ...
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post119633
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com
    

Re: devnp-e1000.so Squelch Test errors  
I'm sorry, Huge!

Correctly I understand that increasing the number of external file descriptors (by receive=nnn argument )  reduces the 
probability of an internal Rx FIFO buffer overran?

Re: devnp-e1000.so Squelch Test errors  
If you really want to stop fifo overruns, you should use flow control.
Increasing the number of descriptors does reduce the probability of fifo overruns, but doesn't prevent them completely.

On 2019-04-10, 8:26 AM, "Leonid Khait" <community-noreply@qnx.com> wrote:

    I'm sorry, Huge!
    
    Correctly I understand that increasing the number of external file descriptors (by receive=nnn argument )  reduces 
the probability of an internal Rx FIFO buffer overran?
    
    
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post119639
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com
    

Re: devnp-e1000.so Squelch Test errors  
Please show: how turn ON flow control of  I211, I217 Ethernet Controllers 
by devnp-e1000.so driver?
Re: devnp-e1000.so Squelch Test errors  
Take a look at the use message for the driver - pause_rx_enable and pause_tx_enable.


On 2019-04-10, 8:59 AM, "Leonid Khait" <community-noreply@qnx.com> wrote:

    Please show: how turn ON flow control of  I211, I217 Ethernet Controllers 
    by devnp-e1000.so driver?
    
    
    
    _______________________________________________
    
    Networking Drivers
    http://community.qnx.com/sf/go/post119641
    To cancel your subscription to this discussion, please e-mail drivers-networking-unsubscribe@community.qnx.com
    

Re: devnp-e1000.so Squelch Test errors  
Thank you , Hugh.